From: Atish Kumar Patra <atishp@rivosinc.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Paolo Bonzini <pbonzini@redhat.com>, KVM <kvm@vger.kernel.org>,
Anup Patel <anup@brainfault.org>,
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: Thu, 21 Apr 2022 14:56:40 -0700 [thread overview]
Message-ID: <CAHBxVyEM4gO2KMP-+cGHLSvriYDuF+TO2JoETh-x1X+bRwuOfA@mail.gmail.com> (raw)
In-Reply-To: <20220422075024.161914a8@canb.auug.org.au>
On Thu, Apr 21, 2022 at 2:50 PM Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> 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.
>
Sorry for that.
This probably happened while copying the fixes tag from mail to the
actual patch.
Let me know if I should resend the patches with correctly formatted fixes tag.
> --
> Cheers,
> Stephen Rothwell
next prev parent reply other threads:[~2022-04-21 21:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-21 21:50 linux-next: Fixes tags need some work in the kvm-fixes tree Stephen Rothwell
2022-04-21 21:56 ` Atish Kumar Patra [this message]
-- 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=CAHBxVyEM4gO2KMP-+cGHLSvriYDuF+TO2JoETh-x1X+bRwuOfA@mail.gmail.com \
--to=atishp@rivosinc.com \
--cc=anup@brainfault.org \
--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).