From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Paul Mackerras <paulus@ozlabs•org>
Cc: Linux Next Mailing List <linux-next@vger•kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Alexey Kardashevskiy <aik@ozlabs•ru>
Subject: linux-next: Fixes tag needs some work in the kvm-ppc tree
Date: Thu, 21 Feb 2019 22:17:53 +1100 [thread overview]
Message-ID: <20190221221753.74e37ec1@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 446 bytes --]
Hi Paul,
In commit
a67614cc05a5 ("KVM: PPC: Release all hardware TCE tables attached to a group")
Fixes tag
Fixes: 121f80ba68f ("KVM: PPC: VFIO: Add in-kernel acceleration for VFIO")
has these problem(s):
- SHA1 should be at least 12 digits long
Can be fixed 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: 488 bytes --]
next reply other threads:[~2019-02-21 11:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-21 11:17 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-01-30 0:31 linux-next: Fixes tag needs some work in the kvm-ppc tree 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=20190221221753.74e37ec1@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=aik@ozlabs$(echo .)ru \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=paulus@ozlabs$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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