All of lore.kernel.org
 help / color / mirror / Atom feed
From: Drew Fustini <fustini@kernel.org>
To: MoeLeak <i@leak.moe>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] riscv: dts: thead: Enable WiFi on Lichee Pi 4A
Date: Thu, 30 Apr 2026 10:26:36 -0700	[thread overview]
Message-ID: <afOQzCLMUZTVlTeL@x1> (raw)
In-Reply-To: <20260426055229.950099-1-i@leak.moe>

On Sun, Apr 26, 2026 at 01:52:29PM +0800, MoeLeak wrote:
> Signed-off-by: MoeLeak <i@leak.moe>

There needs to be proper commit message with a description of why the
change is being made. Please run scripts/checkpatch.pl before
resending as this would have called out the missing commit message.

Also please review Documentation/process/submitting-patches.rst or visit
https://docs.kernel.org/process/submitting-patches.html

Please include revision number in the patch Subject: and also after the
'---' line in the patch so it is easier for a reviewer to know what
changed.

In addition, the To: and Cc: fields are missing several addresses per
MAINTAINERS. Please run scripts/get_maintainer.pl and make sure to
include the recommended addresses. For example:

./scripts/get_maintainer.pl -norolestats --separator="," <patch>

However, I have been using the wonderful b4 script for awhile now and it
makes the above much easier:

https://b4.docs.kernel.org/en/latest/contributor/overview.html

My flow would be something like:

b4 prep -n your-patch-topic # create new branch for your patch
b4 prep --edit-cover # creates the cover letter
b4 prep --auto-to-cc # this adds all the necessary people and lists
b4 prep --check # this runs checkpatch
b4 send --reflect # emails just yourself to review before sending
b4 send # actually posts your patch to the lists

You don't have to use it for this patch but keep it in mind as it can
prevent mistakes and save a lot time.

> ---
>  .../boot/dts/thead/th1520-lichee-pi-4a.dts    | 47 +++++++++++++++++++
>  arch/riscv/boot/dts/thead/th1520.dtsi         | 11 +++++
>  2 files changed, 58 insertions(+)

I think these should be split into two separate patches. The first
patch would add the i2c node in th1520.dtsi and the second patch would
make the changes to th1520-lichee-pi-4a.dts.

Thanks,
Drew

      reply	other threads:[~2026-04-30 17:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-26  5:52 [PATCH] riscv: dts: thead: Enable WiFi on Lichee Pi 4A MoeLeak
2026-04-30 17:26 ` Drew Fustini [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=afOQzCLMUZTVlTeL@x1 \
    --to=fustini@kernel.org \
    --cc=i@leak.moe \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.