From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Paolo Bonzini <pbonzini@redhat.com>, KVM <kvm@vger.kernel.org>
Cc: Wei Wang <wei.w.wang@intel.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: Fixes tag needs some work in the kvm-fixes tree
Date: Fri, 21 Jan 2022 08:14:32 +1100 [thread overview]
Message-ID: <20220121081432.5b671602@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 452 bytes --]
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")
has these problem(s):
- SHA1 should be at least 12 digits long
Can be fixed in the future by setting core.abbrev to 12 (or more) or
(for git v2.11 or later) just making sure it is not set (or set to
"auto").
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 484 bytes --]
next reply other threads:[~2022-01-20 21:14 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-20 21:14 Stephen Rothwell [this message]
2022-01-21 1:42 ` linux-next: Fixes tag needs some work in the kvm-fixes tree Wang, Wei W
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=20220121081432.5b671602@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=wei.w.wang@intel.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).