linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Heiko Stübner" <heiko@sntech.de>
To: Paolo Bonzini <pbonzini@redhat.com>, KVM <kvm@vger.kernel.org>,
	Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Anup Patel <apatel@ventanamicro.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: Fixes tags need some work in the kvm-fixes tree
Date: Tue, 12 Apr 2022 03:07:18 +0200	[thread overview]
Message-ID: <2099797.irdbgypaU6@diego> (raw)
In-Reply-To: <20220412080045.301da5ef@canb.auug.org.au>

Am Dienstag, 12. April 2022, 00:00:45 CEST schrieb Stephen Rothwell:
> Hi all,
> 
> In commit
> 
>   4054eee92902 ("RISC-V: KVM: include missing hwcap.h into vcpu_fp")
> 
> Fixes tag
> 
>   Fixes: 0a86512dc113 ("RISC-V: KVM: Factor-out FP virtualization into separate

hmm, when I sent it [0], the fixes tag was
Fixes: 0a86512dc113 ("RISC-V: KVM: Factor-out FP virtualization into separate sources")

Did it get somehow mangled when the patch got applied?


[0] https://lore.kernel.org/all/20220408092415.1603661-1-heiko@sntech.de/

> 
> has these problem(s):
> 
>   - Subject has leading but no trailing parentheses
>   - Subject has leading but no trailing quotes
> 
> In commit
> 
>   ebdef0de2dbc ("KVM: selftests: riscv: Fix alignment of the guest_hang() function")
> 
> Fixes tag
> 
>   Fixes: 3e06cdf10520 ("KVM: selftests: Add initial support for RISC-V
> 
> has these problem(s):
> 
>   - Subject has leading but no trailing parentheses
>   - Subject has leading but no trailing quotes
> 
> In commit
> 
>   fac372536439 ("KVM: selftests: riscv: Set PTE A and D bits in VS-stage page table")
> 
> Fixes tag
> 
>   Fixes: 3e06cdf10520 ("KVM: selftests: Add initial support for RISC-V
> 
> 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.
> 
> 





  reply	other threads:[~2022-04-12  1:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-11 22:00 linux-next: Fixes tags need some work in the kvm-fixes tree Stephen Rothwell
2022-04-12  1:07 ` Heiko Stübner [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-04-21 21:50 Stephen Rothwell
2022-04-21 21:56 ` Atish Kumar Patra
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=2099797.irdbgypaU6@diego \
    --to=heiko@sntech.de \
    --cc=apatel@ventanamicro.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=pbonzini@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).