mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: "Jan Petrous (OSS)" <jan.petrous@oss.nxp.com>,
	Maxime Coquelin <mcoquelin.stm32@gmail.com>,
	Alexandre Torgue <alexandre.torgue@foss.st.com>
Cc: dl-S32 <S32@nxp.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-stm32@st-md-mailman.stormreply.com"
	<linux-stm32@st-md-mailman.stormreply.com>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	Claudiu Manoil <claudiu.manoil@nxp.com>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [EXT] Re: [PATCH 3/6] dt-bindings: net: Add DT bindings for DWMAC on NXP S32G/R
Date: Mon, 5 Aug 2024 09:17:19 +0200	[thread overview]
Message-ID: <8c78325a-a0c1-4bc9-88dd-3e52296dd656@kernel.org> (raw)
In-Reply-To: <AM9PR04MB8506FC5070BEEE98400247B0E2BE2@AM9PR04MB8506.eurprd04.prod.outlook.com>

On 05/08/2024 09:10, Jan Petrous (OSS) wrote:
>> From: Krzysztof Kozlowski <krzk@kernel.org>
>> Sent: Monday, 5 August, 2024 7:10
>> To: Jan Petrous (OSS) <jan.petrous@oss.nxp.com>; Maxime Coquelin
>> <mcoquelin.stm32@gmail.com>; Alexandre Torgue
>> <alexandre.torgue@foss.st.com>
>> Cc: dl-S32 <S32@nxp.com>; linux-kernel@vger.kernel.org; linux-stm32@st-
>> md-mailman.stormreply.com; linux-arm-kernel@lists.infradead.org; Claudiu
>> Manoil <claudiu.manoil@nxp.com>; netdev@vger.kernel.org
>> Subject: [EXT] Re: [PATCH 3/6] dt-bindings: net: Add DT bindings for DWMAC
>> on NXP S32G/R
>>
>> On 04/08/2024 22:49, Jan Petrous (OSS) wrote:
>>> Add basic description for DWMAC ethernet IP on NXP S32G2xx, S32G3xx
>>> and S32R45 automotive series SoCs.
>>>
>>> Signed-off-by: Jan Petrous (OSS) <jan.petrous@oss.nxp.com>
>>
>> <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>
> 
> Does it mean that scripts/get_maintainer.pl doesn't care about devicetree ML?
> I just tried to recheck, but it still shows me the list I used originally:

It cares and always provides it.

> 
> $ ll outgoing/*.patch
> -rw-rw-r-- 1 hop hop 1998 srp  4 11:33 outgoing/0000-cover-letter.patch
> -rw-rw-r-- 1 hop hop 2518 srp  4 11:33 outgoing/0001-net-driver-stmmac-extend-CSR-calc-support.patch
> -rw-rw-r-- 1 hop hop 2794 srp  4 11:33 outgoing/0002-net-stmmac-Expand-clock-rate-variables.patch
> -rw-rw-r-- 1 hop hop 4427 srp  4 11:33 outgoing/0003-dt-bindings-net-Add-DT-bindings-for-DWMAC-on-NXP-S32.patch
> -rw-rw-r-- 1 hop hop 8610 srp  4 11:33 outgoing/0004-net-stmmac-dwmac-s32cc-add-basic-NXP-S32G-S32R-glue-.patch
> -rw-rw-r-- 1 hop hop 1143 srp  4 11:33 outgoing/0005-MAINTAINERS-Add-Jan-Petrous-as-the-NXP-S32G-R-DWMAC-.patch
> -rw-rw-r-- 1 hop hop 1805 srp  4 11:33 outgoing/0006-net-stmmac-dwmac-s32cc-Read-PTP-clock-rate-when-read.patch
> $ ./scripts/get_maintainer.pl outgoing/*.patch
> Maxime Coquelin <mcoquelin.stm32@gmail.com> (maintainer:ARM/STM32 ARCHITECTURE)
> Alexandre Torgue <alexandre.torgue@foss.st.com> (maintainer:ARM/STM32 ARCHITECTURE)
> "Jan Petrous (OSS)" <jan.petrous@oss.nxp.com> (commit_signer:1/1=100%,authored:1/1=100%,added_lines:46/46=100%,added_lines:61/61=100%,added_lines:69/69=100%,added_lines:165/165=100%,added_lines:298/298=100%,added_lines:35/35=100%,added_lines:51/51=100%)
> linux-kernel@vger.kernel.org (open list)
> linux-stm32@st-md-mailman.stormreply.com (moderated list:ARM/STM32 ARCHITECTURE)
> linux-arm-kernel@lists.infradead.org (moderated list:ARM/STM32 ARCHITECTURE)

Read the form letter carefully. There are several instructions
mentioned. Above commands look sensible but if it still does not work
for you, then I suspect you develop on some old, vendor tree.

BTW, none of other patches made to the list or your threading is
completely broken. See:
https://lore.kernel.org/all/AM9PR04MB85066A2A4D7A2419C1CFC24CE2BD2@AM9PR04MB8506.eurprd04.prod.outlook.com/

Best regards,
Krzysztof


  reply	other threads:[~2024-08-05  7:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-04 20:49 Jan Petrous (OSS)
2024-08-05  5:10 ` Krzysztof Kozlowski
2024-08-05  7:10   ` [EXT] " Jan Petrous (OSS)
2024-08-05  7:17     ` Krzysztof Kozlowski [this message]
2024-08-05  7:29       ` Jan Petrous

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=8c78325a-a0c1-4bc9-88dd-3e52296dd656@kernel.org \
    --to=krzk@kernel.org \
    --cc=S32@nxp.com \
    --cc=alexandre.torgue@foss.st.com \
    --cc=claudiu.manoil@nxp.com \
    --cc=jan.petrous@oss.nxp.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-stm32@st-md-mailman.stormreply.com \
    --cc=mcoquelin.stm32@gmail.com \
    --cc=netdev@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

all inboxes | Powered by JetHome®