From: Gregory CLEMENT <gregory.clement@bootlin.com>
To: Marek Behun <marek.behun@nic.cz>,
Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Andrew Lunn <andrew@lunn.ch>, Jason Cooper <jason@lakedaemon.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Miquel Raynal <miquel.raynal@bootlin.com>,
ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: linux-next: Fixes tags need some work in the mvebu tree
Date: Wed, 09 Oct 2019 09:17:44 +0200 [thread overview]
Message-ID: <87r23ms7zb.fsf@FE-laptop> (raw)
In-Reply-To: <20191008225002.5b95efdf@nic.cz>
Hi Marek,
> On Wed, 9 Oct 2019 07:38:03 +1100
> Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
>> Hi all,
>>
>> In commit
>>
>> 69eea31a26da ("arm64: dts: armada-3720-turris-mox: convert usb-phy to phy-supply")
>>
>> Fixes tag
>>
>> Fixes: eb6c2eb6c7fb ("usb: host: xhci-plat: Prevent an abnormally
>>
>
> This is weird, in the patch I sent the tag ends there with ...")
Truncating the commit title was wrong and checkpatch complained about it
so I fixed on the fly, but unfortunately it was splitted in 2 lines by
my editor and I didn't notice.
It is fixed now
Gregory
>
> Marek
--
Gregory Clement, Bootlin
Embedded Linux and Kernel engineering
http://bootlin.com
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-10-09 7:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-08 20:38 linux-next: Fixes tags need some work in the mvebu tree Stephen Rothwell
2019-10-08 20:50 ` Marek Behun
2019-10-09 7:17 ` Gregory CLEMENT [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-03-14 10:37 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=87r23ms7zb.fsf@FE-laptop \
--to=gregory.clement@bootlin.com \
--cc=andrew@lunn.ch \
--cc=jason@lakedaemon.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=marek.behun@nic.cz \
--cc=miquel.raynal@bootlin.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;
as well as URLs for NNTP newsgroup(s).