public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb•auug.org.au>
To: "Michael S. Tsirkin" <mst@redhat•com>
Cc: Xie Yongji <xieyongji@bytedance•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 vhost tree
Date: Fri, 23 Apr 2021 08:43:19 +1000	[thread overview]
Message-ID: <20210423084319.5cf9dcd8@canb.auug.org.au> (raw)

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

Hi all,

n commit

  a9d064524fc3 ("vhost-vdpa: protect concurrent access to vhost device iotlb")

Fixes tag

  Fixes: 4c8cf318("vhost: introduce vDPA-based backend")

has these problem(s):

  - missing space between the SHA1 and the subject
  - SHA1 should be at least 12 digits long

Probably not worth rebaseing to fix, but can be avoided in the futre
by setting core.abbrev to 12 (or more) or (for git v2.11 or later)
just making sure it is not set (or set to "auto").

-- 
Cheers,
Stephen Rothwell

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

             reply	other threads:[~2021-04-22 22:43 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-22 22:43 Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-08-07 22:22 linux-next: Fixes tag needs some work in the vhost tree Stephen Rothwell
2025-02-24 22:45 Stephen Rothwell
2025-02-25 12:12 ` Michael S. Tsirkin
2022-08-10 22:28 Stephen Rothwell
2021-10-24 21:23 Stephen Rothwell
2021-09-14 21:24 Stephen Rothwell
2021-09-13 23:23 Stephen Rothwell
2021-08-10 22:22 Stephen Rothwell
2020-10-01 22:32 Stephen Rothwell
2020-10-01 23:03 ` si-wei liu
2020-05-02  0:30 Stephen Rothwell
2020-05-05 15:16 ` Stefan Hajnoczi

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=20210423084319.5cf9dcd8@canb.auug.org.au \
    --to=sfr@canb$(echo .)auug.org.au \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=mst@redhat$(echo .)com \
    --cc=xieyongji@bytedance$(echo .)com \
    /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