From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Juergen Gross <jgross@suse.com>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
Stefano Stabellini <sstabellini@kernel.org>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>,
Xen Devel <Xen-devel@lists.xensource.com>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Oleksandr Andrushchenko <oleksandr_andrushchenko@epam.com>
Subject: linux-next: Fixes tag needs some work in the xen-tip tree
Date: Fri, 14 Aug 2020 08:07:14 +1000 [thread overview]
Message-ID: <20200814080714.6aa441cd@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 651 bytes --]
Hi all,
In commit
14dee0586104 ("drm/xen-front: Fix misused IS_ERR_OR_NULL checks")
Fixes tag
Fixes: c575b7eeb89f: "drm/xen-front: Add support for Xen PV display frontend"
has these problem(s):
- missing space between the SHA1 and the subject
- Subject does not match target commit subject
Just use
git log -1 --format='Fixes: %h ("%s")'
Fixes: c575b7eeb89f ("drm/xen-front: Add support for Xen PV display frontend")
Also, please keep all the commit message tags together at the end of
the commit message.
Not worth rebasing over, just to remember for next time, thanks.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2020-08-13 22:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-13 22:07 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-04-06 21:35 linux-next: Fixes tag needs some work in the xen-tip tree Stephen Rothwell
2021-04-06 23:15 ` Boris Ostrovsky
2021-03-10 21:23 Stephen Rothwell
2021-03-10 22:36 ` Boris Ostrovsky
2021-02-22 21:03 Stephen Rothwell
2021-02-22 21:35 ` Boris Ostrovsky
2019-04-25 13:44 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=20200814080714.6aa441cd@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=Xen-devel@lists.xensource.com \
--cc=boris.ostrovsky@oracle.com \
--cc=jgross@suse.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=oleksandr_andrushchenko@epam.com \
--cc=sstabellini@kernel.org \
/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).