[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAHBxVyEM4gO2KMP-+cGHLSvriYDuF+TO2JoETh-x1X+bRwuOfA@mail.gmail.com>
Date: Thu, 21 Apr 2022 14:56:40 -0700
From: Atish Kumar Patra <atishp@...osinc.com>
To: Stephen Rothwell <sfr@...b.auug.org.au>
Cc: Paolo Bonzini <pbonzini@...hat.com>, KVM <kvm@...r.kernel.org>,
Anup Patel <anup@...infault.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: Fixes tags need some work in the kvm-fixes tree
On Thu, Apr 21, 2022 at 2:50 PM Stephen Rothwell <sfr@...b.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
Powered by blists - more mailing lists