linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Joerg Roedel <joro@8bytes.org>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Paul Menzel <pmenzel@molgen.mpg.de>
Subject: linux-next: Fixes tag needs some work in the iommu tree
Date: Wed, 1 Jul 2020 07:01:52 +1000	[thread overview]
Message-ID: <20200701070152.743020ca@canb.auug.org.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 454 bytes --]

Hi all,

In commit

  9a295ff0ffc9 ("iommu/amd: Print extended features in one line to fix divergent log levels")

Fixes tag

  Fixes: 3928aa3f57 ("iommu/amd: Detect and enable guest vAPIC support")

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 --]

             reply	other threads:[~2020-06-30 21:01 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-30 21:01 Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-04-29 13:01 linux-next: Fixes tag needs some work in the iommu tree Stephen Rothwell
2022-05-04  8:33 ` Joerg Roedel
2021-04-15 21:51 Stephen Rothwell
2021-04-16  7:57 ` Dafna Hirschfeld
2020-05-19 18:36 Stephen Rothwell
2020-05-25 11:55 ` Joerg Roedel
2020-03-10 22:36 Stephen Rothwell
2020-03-13 13:26 ` Joerg Roedel
2019-09-01 21:36 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=20200701070152.743020ca@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=joro@8bytes.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=pmenzel@molgen.mpg.de \
    /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).