From: Krzysztof Kozlowski <krzk@kernel.org>
To: Daniel Danzberger <dd@embedd.com>,
catalin.marinas@arm.com, will@kernel.org
Cc: linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] arm64: Add support for airoha en7581 Soc
Date: Mon, 29 Jan 2024 16:20:11 +0100 [thread overview]
Message-ID: <d905f921-927d-4978-acef-6b2822bf9b64@kernel.org> (raw)
In-Reply-To: <20231001122418.2688120-1-dd@embedd.com>
On 01/10/2023 14:24, Daniel Danzberger wrote:
> Hi,
>
> I would like to add linux support for this new platform.
> These 3 patches only add very basic support for the platform and
> it's evaluation board.
>
> The changes contain just some additions to the existing Kconfig and 2 dts files.
You did not get any responses... because of few issues. First, you did
not Cc SoC maintainers, literally no one, so this will be totally
ignored. Second, you missed some lists explicitly asked by
get_maintainers.pl, so this should not be merged anyway. Also, I don't
see checkpatch run on it... so standard disclaimers:
Please use scripts/get_maintainers.pl to get a list of necessary people
and lists to CC (and consider --no-git-fallback argument). 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_getmaintainer.pl provide you proper list of
people, so fix your workflow. Tools might also fail if you work on some
ancient tree (don't, use mainline), work on fork of kernel (don't, use
mainline) or you ignore some maintainers (really don't). Just use b4 and
everything should be fine, although remember about `b4 prep
--auto-to-cc` if you added new patches to the patchset.
Please run scripts/checkpatch.pl and fix reported warnings. Some
warnings can be ignored, but the code here looks like it needs a fix.
Feel free to get in touch if the warning is not clear.
It does not look like you tested the DTS against bindings. Please run
`make dtbs_check W=1` (see
Documentation/devicetree/bindings/writing-schema.rst or
https://www.linaro.org/blog/tips-and-tricks-for-validating-devicetree-sources-with-the-devicetree-schema/
for instructions).
Also, please provide proper maintainers entry. If you do not intend to
be maintainer of it, Cc some of SoC maintainers to get it merged through
them.
Best regards,
Krzysztof
parent reply other threads:[~2024-01-29 15:20 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20231001122418.2688120-1-dd@embedd.com>]
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=d905f921-927d-4978-acef-6b2822bf9b64@kernel.org \
--to=krzk@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=dd@embedd.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=will@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