linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@redhat.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: "Michael S. Tsirkin" <mst@redhat.com>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Fixes tag needs some work in the vhost tree
Date: Tue, 5 May 2020 16:16:21 +0100	[thread overview]
Message-ID: <20200505151621.GE381978@stefanha-x1.localdomain> (raw)
In-Reply-To: <20200502103018.07774059@canb.auug.org.au>

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

On Sat, May 02, 2020 at 10:30:18AM +1000, Stephen Rothwell wrote:
> Hi all,
> 
> In commit
> 
>   ab8be610c87d ("virtio-blk: handle block_device_operations callbacks after hot unplug")
> 
> Fixes tag
> 
>   Fixes: 48e4043d4529523cbc7fa8dd745bd8e2c45ce1d3
> 
> has these problem(s):
> 
>   - missing subject
> 
> Should be
> 
> Fixes: 48e4043d4529 ("virtio: add virtio disk geometry feature")
> 
> Please don't split Fixes tags over more than one line.

Got it, thanks for letting me know. I'll keep the tag on one line in the
future.

Stefan

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

  reply	other threads:[~2020-05-05 15:16 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-02  0:30 linux-next: Fixes tag needs some work in the vhost tree Stephen Rothwell
2020-05-05 15:16 ` Stefan Hajnoczi [this message]
2020-10-01 22:32 Stephen Rothwell
2020-10-01 23:03 ` si-wei liu
2021-04-22 22:43 Stephen Rothwell
2021-08-10 22:22 Stephen Rothwell
2021-09-13 23:23 Stephen Rothwell
2021-09-14 21:24 Stephen Rothwell
2021-10-24 21:23 Stephen Rothwell
2022-08-10 22:28 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=20200505151621.GE381978@stefanha-x1.localdomain \
    --to=stefanha@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mst@redhat.com \
    --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).