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: Yufeng Wang <wangyufeng@kylinos•cn>,
	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: Tue, 25 Feb 2025 09:45:50 +1100	[thread overview]
Message-ID: <20250225094550.07b771f9@canb.auug.org.au> (raw)

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

Hi all,

In commit

  b995427e8a85 ("tools: virtio/linux/module.h add MODULE_DESCRIPTION() define.")

Fixes tag

  Fixes: <ab0727f3ddb8>("virtio: add missing MODULE_DESCRIPTION() macros")

has these problem(s):

  - No SHA1 recognised

In commit

  9709a9145ffe ("tools/virtio: Add DMA_MAPPING_ERROR and sg_dma_len api define for virtio test")

Fixes tag

  Fixes: <c7e1b422afac>("virtio_ring: perform premapped operations based on per-buffer")

has these problem(s):

  - No SHA1 recognised

Fixes tags should be

Fixes: SHA1 ("subject")

Also, please keep all the commit message tags together at the end of
the commit message.

-- 
Cheers,
Stephen Rothwell

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

             reply	other threads:[~2025-02-24 22:45 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-24 22:45 Stephen Rothwell [this message]
2025-02-25 12:12 ` linux-next: Fixes tag needs some work in the vhost tree Michael S. Tsirkin
  -- strict thread matches above, loose matches on Subject: below --
2025-08-07 22:22 Stephen Rothwell
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
2021-04-22 22:43 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=20250225094550.07b771f9@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=wangyufeng@kylinos$(echo .)cn \
    /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