All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@kernel.org>
To: Alain Volmat <avolmat@me.com>
Cc: Arnd Bergmann <arnd@arndb.de>, Olof Johansson <olof@lixom.net>,
	SoC Team <soc@kernel.org>,  Rob Herring <robh+dt@kernel.org>,
	Patrice Chotard <patrice.chotard@st.com>,
	 Linux ARM <linux-arm-kernel@lists.infradead.org>,
	DTML <devicetree@vger.kernel.org>,
	 "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] ARM: dts: sti: add the spinor controller node within stih407-family
Date: Thu, 28 Jan 2021 14:05:41 +0100	[thread overview]
Message-ID: <CAK8P3a1RmN+MQoZSVA+ekMORLZdmTHtoEWtcPUzJLVujLCThXQ@mail.gmail.com> (raw)
In-Reply-To: <20210128075806.10318-1-avolmat@me.com>

On Thu, Jan 28, 2021 at 8:58 AM Alain Volmat <avolmat@me.com> wrote:
>
> add the spinor controller node within stih407-family.
>
> Signed-off-by: Alain Volmat <avolmat@me.com>

dts changes look ok to me, but please resend considering:

- Add a proper changelog text, rather than repeating the subject in the
  body. I'm sure you can find something useful to say about this change:
  Why do you need this controller? Why was this not originally part
  of the .dtsi file?

- Address your patches to the correct recipients. I see you have eight
  addresses on 'To:' and only yourself on 'Cc'. Try to find out who would
  be the person to pick up the patches and send it only to them, with
  others in Cc. soc@kernel.org should not be in either list here, because
  that just means we get it in patchwork for the soc tree, but these should
  be picked up by the platform maintainer and forward to us from there.

         Arnd

WARNING: multiple messages have this Message-ID (diff)
From: Arnd Bergmann <arnd@kernel.org>
To: Alain Volmat <avolmat@me.com>
Cc: DTML <devicetree@vger.kernel.org>, Arnd Bergmann <arnd@arndb.de>,
	Patrice Chotard <patrice.chotard@st.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	SoC Team <soc@kernel.org>, Rob Herring <robh+dt@kernel.org>,
	Olof Johansson <olof@lixom.net>,
	Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 1/2] ARM: dts: sti: add the spinor controller node within stih407-family
Date: Thu, 28 Jan 2021 14:05:41 +0100	[thread overview]
Message-ID: <CAK8P3a1RmN+MQoZSVA+ekMORLZdmTHtoEWtcPUzJLVujLCThXQ@mail.gmail.com> (raw)
Message-ID: <20210128130541.ry8uiW_pCpTWiSbtmoneb6i4phjZELQZ5oLzCVQCgVM@z> (raw)
In-Reply-To: <20210128075806.10318-1-avolmat@me.com>

On Thu, Jan 28, 2021 at 8:58 AM Alain Volmat <avolmat@me.com> wrote:
>
> add the spinor controller node within stih407-family.
>
> Signed-off-by: Alain Volmat <avolmat@me.com>

dts changes look ok to me, but please resend considering:

- Add a proper changelog text, rather than repeating the subject in the
  body. I'm sure you can find something useful to say about this change:
  Why do you need this controller? Why was this not originally part
  of the .dtsi file?

- Address your patches to the correct recipients. I see you have eight
  addresses on 'To:' and only yourself on 'Cc'. Try to find out who would
  be the person to pick up the patches and send it only to them, with
  others in Cc. soc@kernel.org should not be in either list here, because
  that just means we get it in patchwork for the soc tree, but these should
  be picked up by the platform maintainer and forward to us from there.

         Arnd

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2021-01-28 13:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-28  7:58 [PATCH 1/2] ARM: dts: sti: add the spinor controller node within stih407-family Alain Volmat
2021-01-28  7:58 ` Alain Volmat
2021-01-28 13:05 ` Arnd Bergmann [this message]
2021-01-28 13:05   ` Arnd Bergmann

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=CAK8P3a1RmN+MQoZSVA+ekMORLZdmTHtoEWtcPUzJLVujLCThXQ@mail.gmail.com \
    --to=arnd@kernel.org \
    --cc=arnd@arndb.de \
    --cc=avolmat@me.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=olof@lixom.net \
    --cc=patrice.chotard@st.com \
    --cc=robh+dt@kernel.org \
    --cc=soc@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 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.