linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Paolo Bonzini <pbonzini@redhat.com>, KVM <kvm@vger.kernel.org>
Cc: Atish Patra <atishp@rivosinc.com>,
	Anup Patel <anup@brainfault.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: Fixes tags need some work in the kvm-fixes tree
Date: Fri, 22 Apr 2022 07:50:24 +1000	[thread overview]
Message-ID: <20220422075024.161914a8@canb.auug.org.au> (raw)

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

Hi all,

In commit

  38d9a4ac65f2 ("RISC-V: KVM: Restrict the extensions that can be disabled")

Fixes tag

  Fixes: 92ad82002c39 ("RISC-V: KVM: Implement

has these problem(s):

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

In commit

  3ab75a793e49 ("RISC-V: KVM: Remove 's' & 'u' as valid ISA extension")

Fixes tag

  Fixes: a33c72faf2d7 ("RISC-V: KVM: Implement VCPU create, init and

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.

-- 
Cheers,
Stephen Rothwell

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

             reply	other threads:[~2022-04-21 21:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-21 21:50 Stephen Rothwell [this message]
2022-04-21 21:56 ` linux-next: Fixes tags need some work in the kvm-fixes tree Atish Kumar Patra
  -- strict thread matches above, loose matches on Subject: below --
2022-04-11 22:00 Stephen Rothwell
2022-04-12  1:07 ` Heiko Stübner
2020-08-02 11:11 Stephen Rothwell
2020-03-03 20:39 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=20220422075024.161914a8@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=anup@brainfault.org \
    --cc=atishp@rivosinc.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    /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).