From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Jason Cooper <jason@lakedaemon•net>, Andrew Lunn <andrew@lunn•ch>,
Gregory Clement <gregory.clement@bootlin•com>,
ARM <linux-arm-kernel@lists•infradead.org>
Cc: "Miquel Raynal" <miquel.raynal@bootlin•com>,
"Linux Next Mailing List" <linux-next@vger•kernel.org>,
"Linux Kernel Mailing List" <linux-kernel@vger•kernel.org>,
"Marek Behún" <marek.behun@nic•cz>
Subject: linux-next: Fixes tags need some work in the mvebu tree
Date: Wed, 9 Oct 2019 07:38:03 +1100 [thread overview]
Message-ID: <20191009073803.633c02b5@canb.auug.org.au> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 762 bytes --]
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
has these problem(s):
- Subject has leading but no trailing parentheses
- Subject has leading but no trailing quotes
Please do not split Fxes tags across more than one line.
In commit
46cb29381635 ("arm64: dts: marvell: Add AP806-dual missing CPU clocks")
Fixes tag
Fixes: e043bbd61e01 ("arm64: dts: marvell: Add cpu clock node on Armada 7K/8K")
has these problem(s):
- Target SHA1 does not exist
Did you mean
Fixes: c00bc38354cf ("arm64: dts: marvell: Add cpu clock node on Armada 7K/8K")
--
Cheers,
Stephen Rothwell
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists•infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2019-10-08 20:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-08 20:38 Stephen Rothwell [this message]
2019-10-08 20:50 ` linux-next: Fixes tags need some work in the mvebu tree Marek Behun
2019-10-09 7:17 ` Gregory CLEMENT
-- 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=20191009073803.633c02b5@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=andrew@lunn$(echo .)ch \
--cc=gregory.clement@bootlin$(echo .)com \
--cc=jason@lakedaemon$(echo .)net \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=marek.behun@nic$(echo .)cz \
--cc=miquel.raynal@bootlin$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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