From: Shawn Guo <shawn.guo@linaro.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Daniel Baluta <daniel.baluta@nxp.com>
Subject: Re: linux-next: Fixes tag needs some work in the imx-mxs tree
Date: Thu, 17 Jan 2019 08:36:58 +0800 [thread overview]
Message-ID: <20190117003655.GA19069@dragon> (raw)
In-Reply-To: <20190117075459.50e6a22f@canb.auug.org.au>
On Thu, Jan 17, 2019 at 07:54:59AM +1100, Stephen Rothwell wrote:
> Hi Shawn,
>
> Commit
>
> fde7ed930ca2 ("arm64: dts: imx8qxp: Fix MU4_INT number")
>
> has a malformed Fixes tag.
>
> The SHA1 should be at least 12 digits long.
Fixed. Thanks for spotting it, Stephen.
Shawn
next prev parent reply other threads:[~2019-01-17 0:36 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-16 20:54 linux-next: Fixes tag needs some work in the imx-mxs tree Stephen Rothwell
2019-01-17 0:36 ` Shawn Guo [this message]
2019-06-06 21:46 Stephen Rothwell
2019-06-07 0:24 ` Shawn Guo
2019-06-11 8:36 ` Peng Fan
2019-06-12 10:51 ` Shawn Guo
2019-06-12 12:15 ` Peng Fan
2020-11-01 21:24 Stephen Rothwell
2020-11-02 0:02 ` Shawn Guo
2020-11-02 8:47 ` Oleksij Rempel
2021-07-14 22:04 Stephen Rothwell
2021-07-15 11:03 ` Shawn Guo
2022-01-29 23:18 Stephen Rothwell
2022-04-18 20:50 Stephen Rothwell
2022-04-19 8:15 ` Max Krummenacher
2022-06-13 21:41 Stephen Rothwell
2022-09-05 21:37 Stephen Rothwell
2022-09-06 7:22 ` Marcel Ziswiler
2022-09-06 7:49 ` Shawn Guo
2022-09-13 10:15 Stephen Rothwell
2022-09-13 17:08 ` Tim Harvey
2022-09-14 3:48 ` Shawn Guo
2022-09-14 15:11 ` Tim Harvey
2022-10-24 4:37 Stephen Rothwell
2022-10-24 6:50 ` Francesco Dolcini
2022-10-24 7:07 ` Marcel Ziswiler
2022-10-29 8:27 ` Shawn Guo
2023-11-27 4:25 Stephen Rothwell
2023-12-06 4:47 Stephen Rothwell
2023-12-06 5:25 ` Shawn Guo
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=20190117003655.GA19069@dragon \
--to=shawn.guo@linaro.org \
--cc=daniel.baluta@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--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).