From: Krzysztof Kozlowski <krzk@kernel.org>
To: philmb3487 <philmb3487@proton.me>,
"linux-arm-msm@vger.kernel.org" <linux-arm-msm@vger.kernel.org>
Subject: Re: [PATCH] dt-bindings: arm: qcom,ids: Add SoC IDs for SM8635 family
Date: Sun, 16 Nov 2025 12:04:18 +0100 [thread overview]
Message-ID: <66d58b6c-aefd-4848-882b-51770f7020f3@kernel.org> (raw)
In-Reply-To: <9nTdr-7UlyytB3d5Iz0IEGrAAzjPipf4NEiZvLMmpk9OmCmRuL346OxjZgpLkLdG7dFYE_rj-5aibg7bhYHrQmjwo1e096-2IGhfi1rKglE=@proton.me>
On 16/11/2025 01:43, philmb3487 wrote:
> Author: Philippe Michaud-Boudreault <philmb3487@proton.me>
> Date: Sat Nov 15 19:41:12 2025 -0500
>
> dt-bindings: arm: qcom,ids: Add SoC IDs for SM8635 family
>
> Add the SoC ID for the SM8635.
1. Unfortunately this looks like a messed up patch header. Please use
standard tools for sending patches.
2. Also missing SoB.
3. Also, missing users of this - you have to organize your work in
proper patchsets. See recent guide on Linaro.org blog how to send patches.
... and finally:
Please use scripts/get_maintainers.pl to get a list of necessary people
and lists to CC (and consider --no-git-fallback argument, so you will
not CC people just because they made one commit years ago). 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.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-11-16 11:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-16 0:43 [PATCH] dt-bindings: arm: qcom,ids: Add SoC IDs for SM8635 family philmb3487
2025-11-16 11:04 ` Krzysztof Kozlowski [this message]
2025-11-16 15:13 ` philmb3487
2025-11-16 15:24 ` Krzysztof Kozlowski
2025-11-16 17:39 ` Dmitry Baryshkov
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=66d58b6c-aefd-4848-882b-51770f7020f3@kernel.org \
--to=krzk@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=philmb3487@proton.me \
/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.