linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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: Luca Fancellu <luca.fancellu@arm.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: Fixes tag needs some work in the xen-tip tree
Date: Wed, 7 Apr 2021 07:35:04 +1000	[thread overview]
Message-ID: <20210407073504.0758735d@canb.auug.org.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 488 bytes --]

Hi all,

In commit

  da3b45cbcb0f ("xen/evtchn: Change irq_info lock to raw_spinlock_t")

Fixes tag

  Fixes: 25da4618af24 ("xen/events: don't unmask an event channel

has these problem(s):

  - Subject has leading but no trailing parentheses
  - Subject has leading but no trailing quotes

Please do not split Fixes tags over more than one line.  Also, please
keep all the commit message tags together at the end of te commit message.

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

             reply	other threads:[~2021-04-06 21:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-06 21:35 Stephen Rothwell [this message]
2021-04-06 23:15 ` linux-next: Fixes tag needs some work in the xen-tip tree Boris Ostrovsky
  -- strict thread matches above, loose matches on Subject: below --
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
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=20210407073504.0758735d@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=luca.fancellu@arm.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).