[PATCH v2 0/3] arm64: dts: qcom: Refine device support for Xiaomi Redmi 5A

Reza Kurniawan posted 3 patches 1 month, 2 weeks ago
There is a newer version of this series
.../boot/dts/qcom/msm8917-xiaomi-riva.dts     | 36 +++++++++++++++++++
1 file changed, 36 insertions(+)
[PATCH v2 0/3] arm64: dts: qcom: Refine device support for Xiaomi Redmi 5A
Posted by Reza Kurniawan 1 month, 2 weeks ago
Thank you for the feedback. This is my first contribution and I'm not
quite familiar with the process yet, apologies for the mistakes.

As instructed, I've added my name in the Signed-off-by field. Aside from
that, since the changes are isolated from each other, the patch is split
into multiple patches.

Changes in v2:
- Split the patch into multiple patches.
- Change name in Signed-off-by field.

v1: https://lore.kernel.org/r/20260810062611.735673-2-imkyufie@gmail.com

Reza Kurniawan (3):
  arm64: dts: qcom: Add UART support for Xiaomi Redmi 5A (riva)
  arm64: dts: qcom: Add haptic vibrator support for Xiaomi Redmi 5A
    (riva)
  arm64: dts: qcom: Add notification LED support for Xiaomi Redmi 5A
    (riva)

 .../boot/dts/qcom/msm8917-xiaomi-riva.dts     | 36 +++++++++++++++++++
 1 file changed, 36 insertions(+)


base-commit: 6b8c8af514d739d0335f5579b585e02babe8a727
-- 
2.55.0
Re: [PATCH v2 0/3] arm64: dts: qcom: Refine device support for Xiaomi Redmi 5A
Posted by Konrad Dybcio 1 month, 1 week ago
On 8/10/26 12:53 PM, Reza Kurniawan wrote:
> Thank you for the feedback. This is my first contribution and I'm not
> quite familiar with the process yet, apologies for the mistakes.
> 
> As instructed, I've added my name in the Signed-off-by field. Aside from
> that, since the changes are isolated from each other, the patch is split
> into multiple patches.

You're on good track. Please make sure all of the commits, apart from a
suitable title, also come with a commit message. This is important both
for the reviewer to more easily grok the change (or have confidence in
your understanding on the problem), as well as it brings historical
value for people that come after you - they can learn from your notes.

See: https://docs.kernel.org/process/submitting-patches.html#describe-your-changeslore

For the patch submission itself, there's a tool called b4 that takes
care of some of the headaches for you:

https://b4.docs.kernel.org/

Konrad