From: Boris Ostrovsky <boris.ostrovsky@oracle•com>
To: Stephen Rothwell <sfr@canb•auug.org.au>,
Juergen Gross <jgross@suse•com>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle•com>,
Stefano Stabellini <sstabellini@kernel•org>,
Xen Devel <Xen-devel@lists•xensource.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: Re: linux-next: Fixes tag needs some work in the xen-tip tree
Date: Wed, 10 Mar 2021 17:36:38 -0500 [thread overview]
Message-ID: <0577a59f-cf6f-cb26-8898-311e70b93593@oracle.com> (raw)
In-Reply-To: <20210311082354.0f149e1c@canb.auug.org.au>
On 3/10/21 4:23 PM, Stephen Rothwell wrote:
> Hi all,
>
> In commit
>
> 1103e2826a9f ("xen/events: don't unmask an event channel when an eoi is pending")
>
> Fixes tag
>
> Fixes: 54c9de89895e0a36047 ("xen/events: add a new late EOI evtchn framework")
>
> has these problem(s):
>
> - Subject does not match target commit subject
> Just use
> git log -1 --format='Fixes: %h ("%s")'
Sigh... Missed this again. Updated to
Fixes: 54c9de89895e ("xen/events: add a new "late EOI" evtchn framework")
-boris
next prev parent reply other threads:[~2021-03-10 22:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-10 21:23 linux-next: Fixes tag needs some work in the xen-tip tree Stephen Rothwell
2021-03-10 22:36 ` Boris Ostrovsky [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-04-06 21:35 Stephen Rothwell
2021-04-06 23:15 ` Boris Ostrovsky
2021-02-22 21:03 Stephen Rothwell
2021-02-22 21:35 ` Boris Ostrovsky
2020-08-13 22:07 Stephen Rothwell
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=0577a59f-cf6f-cb26-8898-311e70b93593@oracle.com \
--to=boris.ostrovsky@oracle$(echo .)com \
--cc=Xen-devel@lists$(echo .)xensource.com \
--cc=jgross@suse$(echo .)com \
--cc=konrad.wilk@oracle$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
--cc=sstabellini@kernel$(echo .)org \
/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