From: Sudeep Holla <sudeep.holla@arm.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Olof Johansson <olof@lixom.net>, Arnd Bergmann <arnd@arndb.de>,
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>,
Sudeep Holla <sudeep.holla@arm.com>
Subject: Re: linux-next: Fixes tag needs some work in the arm-soc tree
Date: Thu, 14 Nov 2019 11:01:23 +0000 [thread overview]
Message-ID: <20191114110123.GA18036@bogus> (raw)
In-Reply-To: <20191114202122.0f38eab6@canb.auug.org.au>
On Thu, Nov 14, 2019 at 08:21:22PM +1100, Stephen Rothwell wrote:
> Hi all,
>
> n commit
>
> 9a6edfe32f37 ("firmware: arm_scmi: Fix doorbell ring logic for !CONFIG_64BIT")
>
> Fixes tag
>
> Fixes: 823839571d76 ("firmware: arm_scmi: Make use SCMI v2.0 fastchannel
>
> has these problem(s):
>
> - Subject has leading but no trailing parentheses
> - Subject has leading but no trailing quotes
>
> Please do not split Fixes tags over more than one line.
>
My bad, and sorry for that, it was too long and hence I split it into 2 lines.
--
Regards,
Sudeep
next prev parent reply other threads:[~2019-11-14 11:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-14 9:21 linux-next: Fixes tag needs some work in the arm-soc tree Stephen Rothwell
2019-11-14 11:01 ` Sudeep Holla [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-02-28 15:51 Stephen Rothwell
2022-02-28 15:57 ` Arnd Bergmann
2020-10-05 9:21 Stephen Rothwell
2020-01-12 19:56 Stephen Rothwell
2020-01-12 20:01 ` Olof Johansson
2019-09-04 21:24 Stephen Rothwell
2019-08-15 21:43 Stephen Rothwell
2019-08-15 10:10 Stephen Rothwell
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=20191114110123.GA18036@bogus \
--to=sudeep.holla@arm.com \
--cc=arnd@arndb.de \
--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).