From: Alexandre TORGUE <alexandre.torgue@st.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Patrice CHOTARD - foss <patrice.chotard@foss.st.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: RE: linux-next: Fixes tags need some work in the stm32 tree
Date: Tue, 10 Jan 2023 08:22:06 +0000 [thread overview]
Message-ID: <AS8PR10MB47121F3C3C9148E48748ACBFEEFF9@AS8PR10MB4712.EURPRD10.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <20230110084159.7d20dd38@canb.auug.org.au>
Hi Stephen
ST Restricted
> -----Original Message-----
> From: Stephen Rothwell <sfr@canb.auug.org.au>
> Sent: Monday, January 9, 2023 10:42 PM
> To: Alexandre TORGUE <alexandre.torgue@st.com>
> Cc: Patrice CHOTARD - foss <patrice.chotard@foss.st.com>; Linux Kernel
> Mailing List <linux-kernel@vger.kernel.org>; Linux Next Mailing List
> <linux- next@vger.kernel.org>
> Subject: linux-next: Fixes tags need some work in the stm32 tree
>
> Hi all,
>
> In commits
>
> 731c05eb8ec3 ("ARM: dts: stm32: Fix qspi pinctrl phandle for
> stm32mp151a-
> prtt1l")
> 1bfe5bf6a0ab ("ARM: dts: stm32: Fix qspi pinctrl phandle for
> stm32mp157c-
> emstamp-argon")
> b8deada61dd2 ("ARM: dts: stm32: Fix qspi pinctrl phandle for
> stm32mp15xx-
> dhcom-som")
> 4beb2a5e840a ("ARM: dts: stm32: Fix qspi pinctrl phandle for
> stm32mp15xx-
> dhcor-som")
>
> Fixes tag
>
> Fixes: ea99a5a02ebc ("ARM: dts: stm32: Create separate pinmux for
> qspi cs pin in stm32mp15-pinctrl.dtsi)
>
> has these problem(s):
>
> - Subject has leading but no trailing quotes
>
> Also, please keep all the commit message tags together at the end of
> the commit message. And I don't see any point in the "To:" tag.
I just updated the branch. Sorry to have missed it.
Cheers
Alex
>
> --
> Cheers,
> Stephen Rothwell
prev parent reply other threads:[~2023-01-10 8:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-09 21:41 Stephen Rothwell
2023-01-10 8:22 ` Alexandre TORGUE [this message]
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=AS8PR10MB47121F3C3C9148E48748ACBFEEFF9@AS8PR10MB4712.EURPRD10.PROD.OUTLOOK.COM \
--to=alexandre.torgue@st.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=patrice.chotard@foss.st.com \
--cc=sfr@canb.auug.org.au \
/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®