All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Wang, Wei W" <wei.w.wang@intel.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
	Paolo Bonzini <pbonzini@redhat.com>, KVM <kvm@vger.kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	"Linux Next Mailing List" <linux-next@vger.kernel.org>
Subject: RE: linux-next: Fixes tag needs some work in the kvm-fixes tree
Date: Fri, 21 Jan 2022 01:42:50 +0000	[thread overview]
Message-ID: <52efe36ef887430ba27ad718afc55a5d@intel.com> (raw)
In-Reply-To: <20220121081432.5b671602@canb.auug.org.au>

On Friday, January 21, 2022 5:15 AM, Stephen Rothwell wrote:
> Hi all,
> 
> In commit
> 
>   1a1d1dbce6d5 ("kvm: selftests: conditionally build vm_xsave_req_perm()")
> 
> Fixes tag
> 
>   Fixes: 415a3c33e8 ("kvm: selftests: Add support for KVM_CAP_XSAVE2")

OK, for 12 digits, it should be: 415a3c33e847

Paolo, would you like to change it directly or need me to resend the patch?

Thanks,
Wei

  reply	other threads:[~2022-01-21  1:42 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-20 21:14 linux-next: Fixes tag needs some work in the kvm-fixes tree Stephen Rothwell
2022-01-21  1:42 ` Wang, Wei W [this message]
2022-01-21  2:14   ` Stephen Rothwell
  -- strict thread matches above, loose matches on Subject: below --
2024-02-06 20:36 Stephen Rothwell
2023-01-24 20:38 Stephen Rothwell
2023-01-12 21:27 Stephen Rothwell
2022-10-23 21:00 Stephen Rothwell
2022-04-12 21:03 Stephen Rothwell
2022-04-06 21:48 Stephen Rothwell
2021-12-05 14:33 Stephen Rothwell
2021-11-17 21:23 Stephen Rothwell
2021-09-30 22:28 Stephen Rothwell
2021-09-26 21:28 Stephen Rothwell
2021-07-14 21:59 Stephen Rothwell
2021-05-24 21:59 Stephen Rothwell
2020-11-08 21:14 Stephen Rothwell
2020-11-09  9:43 ` Maxim Levitsky
2020-09-13  8:37 Stephen Rothwell
2020-05-27 21:47 Stephen Rothwell
2020-05-06 18:43 Stephen Rothwell
2019-08-21 13:21 Stephen Rothwell
2019-05-01 12:06 Stephen Rothwell
2019-04-30 22:01 Stephen Rothwell
2019-04-22 21:01 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=52efe36ef887430ba27ad718afc55a5d@intel.com \
    --to=wei.w.wang@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.