linux-arm-msm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: "Eric Gonçalves" <ghatto404@gmail.com>, linux-arm-msm@vger.kernel.org
Cc: konradybcio@kernel.org
Subject: Re: [PATCH v5 0/2] arm64: dts: qcom: add initial support for Samsung Galaxy S22
Date: Tue, 17 Jun 2025 08:02:12 +0200	[thread overview]
Message-ID: <ae7e77ef-4ed9-4cab-b10d-27f780449adf@kernel.org> (raw)
In-Reply-To: <20250616090250.36605-1-ghatto404@gmail.com>

On 16/06/2025 11:02, Eric Gonçalves wrote:
> Changes in v5:
> - Properly format the thread
> 
> Changes in v4:
> - Try to properly format the thread
> 
> Changes in v3:
> - Removed unnecessary initrd start and end addresses
> - Make sure r0q is in right order on Makefile
> - Properly format memory addresses
> - Set r0q to the correct, alphabetical order in documents
> 
> I'm sorry for my mistakes, this is my first patch and I got
> a bit confused on how the whole patch system works. 
> I hope that is cleared up.
> 
Can you slow down please? One patchset per day.

<form letter>
Please use scripts/get_maintainers.pl to get a list of necessary people
and lists to CC. It might happen, that command when run on an older
kernel, gives you outdated entries. Therefore please be sure you base
your patches on recent Linux kernel.

Tools like b4 or scripts/get_maintainer.pl provide you proper list of
people, so fix your workflow. Tools might also fail if you work on some
ancient tree (don't, instead use mainline) or work on fork of kernel
(don't, instead use mainline). Just use b4 and everything should be
fine, although remember about `b4 prep --auto-to-cc` if you added new
patches to the patchset.

You missed at least devicetree list (maybe more), so this won't be
tested by automated tooling. Performing review on untested code might be
a waste of time.

Please kindly resend and include all necessary To/Cc entries.
</form letter>

Best regards,
Krzysztof

  parent reply	other threads:[~2025-06-17  6:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-16  9:02 [PATCH v5 0/2] arm64: dts: qcom: add initial support for Samsung Galaxy S22 Eric Gonçalves
2025-06-16  9:02 ` [PATCH v5 1/2] dt-bindings: arm: qcom: document r0q board binding Eric Gonçalves
2025-06-16  9:02 ` [PATCH v5 2/2] arm64: dts: qcom: add initial support for Samsung Galaxy S22 Eric Gonçalves
2025-06-17  9:10   ` Krzysztof Kozlowski
2025-06-16 11:39 ` [PATCH v5 0/2] " Konrad Dybcio
2025-06-16 21:46 ` Rob Herring (Arm)
2025-06-17  6:02 ` Krzysztof Kozlowski [this message]
2025-06-17  6:04   ` Krzysztof Kozlowski

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=ae7e77ef-4ed9-4cab-b10d-27f780449adf@kernel.org \
    --to=krzk@kernel.org \
    --cc=ghatto404@gmail.com \
    --cc=konradybcio@kernel.org \
    --cc=linux-arm-msm@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).