From: Arnd Bergmann <arnd@arndb.de>
To: Alexandre Torgue <alexandre.torgue@st.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Olof Johansson <olof@lixom.net>,
ARM <linux-arm-kernel@lists.infradead.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Fabrice Gasnier <fabrice.gasnier@st.com>
Subject: Re: linux-next: Fixes tags need some work in the arm-soc tree
Date: Tue, 27 Aug 2019 15:07:02 +0200 [thread overview]
Message-ID: <CAK8P3a1M94LwpVhJe8eLG-JMr+wEuACZZ=_=N3ws5x9yP9SnLg@mail.gmail.com> (raw)
In-Reply-To: <f4e0e924-03ea-bf63-85a0-5718874ceb38@st.com>
On Mon, Aug 26, 2019 at 11:44 AM Alexandre Torgue
<alexandre.torgue@st.com> wrote:
> On 8/13/19 11:47 PM, Stephen Rothwell wrote:
> > Hi Arnd,
> >
> > On Tue, 13 Aug 2019 21:35:58 +0200 Arnd Bergmann <arnd@arndb.de> wrote:
> >>
> >> On Tue, Aug 13, 2019 at 4:28 PM Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> >>
> >>>
> >>> Please do not split Fixes tags over more than one line. Also, please
> >>> keep them with the rest of the other tags.
> >>
> >> Thanks for the report. How bad is this? Should I undo the merge and
> >> wait for an updated pull request?
> >
> > Its probably ok to leave as long as lessons are learnt :-)
> >
>
> Sorry for my late answer.
>
> Thanks Stephen for information. I'll take care next time before merging
> patches with "fixes" tag.
>
> Arnd, no need to update the PR ?
No, since it's already pulled, just leave it for this time.
Arnd
prev parent reply other threads:[~2019-08-27 13:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-13 14:28 linux-next: Fixes tags need some work in the arm-soc tree Stephen Rothwell
2019-08-13 19:35 ` Arnd Bergmann
2019-08-13 21:47 ` Stephen Rothwell
2019-08-26 9:44 ` Alexandre Torgue
2019-08-27 13:07 ` Arnd Bergmann [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='CAK8P3a1M94LwpVhJe8eLG-JMr+wEuACZZ=_=N3ws5x9yP9SnLg@mail.gmail.com' \
--to=arnd@arndb.de \
--cc=alexandre.torgue@st.com \
--cc=fabrice.gasnier@st.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=olof@lixom.net \
--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;
as well as URLs for NNTP newsgroup(s).