linux-crypto.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: linux-crypto@vger.kernel.org,
	Herbert Xu <herbert@gondor.apana.org.au>,
	"David S . Miller" <davem@davemloft.net>,
	phone-devel@vger.kernel.org, Stefan Hansson <newbyte@disroot.org>,
	Lionel Debieve <lionel.debieve@foss.st.com>,
	Maxime Coquelin <mcoquelin.stm32@gmail.com>,
	Alexandre Torgue <alexandre.torgue@foss.st.com>,
	devicetree@vger.kernel.org
Subject: Re: [PATCH v1 1/4] dt-bindings: crypto: Let STM32 define Ux500 CRYP
Date: Thu, 24 Nov 2022 10:22:38 +0100	[thread overview]
Message-ID: <7b11aca1-c984-d8f4-6d99-13833270ee16@kernel.org> (raw)
In-Reply-To: <CACRpkdZsxk2MH0AEHE=kpHuikdP35d3_q6wrr3+Yrs2QpZy62A@mail.gmail.com>

On 23/11/2022 22:35, Linus Walleij wrote:
> On Wed, Nov 23, 2022 at 5:13 PM Krzysztof Kozlowski <krzk@kernel.org> wrote:
> 
>>> Cc: devicetree@vger.kernel.org
>>> Cc: Lionel Debieve <lionel.debieve@foss.st.com>
>>> Cc: Maxime Coquelin <mcoquelin.stm32@gmail.com>
>>> Cc: Alexandre Torgue <alexandre.torgue@foss.st.com>
>>> Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
> (...)
>>
>> 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.
> 
> The people reported by get_maintainers are maybe not on the CC
> line of the patch, but if you look at the mail header they are
> on the Cc: line... because I pass the not immediately relevant people
> to git-send-email rather than add them in the Cc tags.

I am referring to the mail header, not to "CC" lines above. You missed
to Cc Devicetree maintainers (maybe more folks, I did not check all
addresses).

get_maintainers.pl would give you proper addresses.

Best regards,
Krzysztof


  reply	other threads:[~2022-11-24  9:22 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-19 22:12 [PATCH v1 0/4] crypto: stm32 - reuse for Ux500 Linus Walleij
2022-11-19 22:12 ` [PATCH v1 1/4] dt-bindings: crypto: Let STM32 define Ux500 CRYP Linus Walleij
2022-11-23 16:13   ` Krzysztof Kozlowski
2022-11-23 21:35     ` Linus Walleij
2022-11-24  9:22       ` Krzysztof Kozlowski [this message]
2022-11-24 10:29         ` Linus Walleij
2022-11-19 22:12 ` [PATCH v1 2/4] crypto: stm32 - enable drivers to be used on Ux500 Linus Walleij
     [not found]   ` <b0b346ca-7b47-758a-c9e7-e7fda2b0856b@foss.st.com>
2022-11-21 14:05     ` Linus Walleij
2022-11-19 22:12 ` [PATCH v1 3/4] crypto: stm32/cryp - enable for use with Ux500 Linus Walleij
     [not found]   ` <8f55596e-12e3-8968-ebe5-e90be38ca5cb@foss.st.com>
2022-11-21 14:07     ` Linus Walleij
2022-11-19 22:12 ` [PATCH v1 4/4] crypto: ux500/cryp - delete driver Linus Walleij

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=7b11aca1-c984-d8f4-6d99-13833270ee16@kernel.org \
    --to=krzk@kernel.org \
    --cc=alexandre.torgue@foss.st.com \
    --cc=davem@davemloft.net \
    --cc=devicetree@vger.kernel.org \
    --cc=herbert@gondor.apana.org.au \
    --cc=linus.walleij@linaro.org \
    --cc=linux-crypto@vger.kernel.org \
    --cc=lionel.debieve@foss.st.com \
    --cc=mcoquelin.stm32@gmail.com \
    --cc=newbyte@disroot.org \
    --cc=phone-devel@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).