From: Joerg Roedel <joro@8bytes.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Vasant Hegde <vasant.hegde@amd.com>,
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 iommu tree
Date: Fri, 14 Feb 2025 09:13:42 +0100 [thread overview]
Message-ID: <Z677NjlRfHdOmdiy@8bytes.org> (raw)
In-Reply-To: <20250212081251.0a1eda6d@canb.auug.org.au>
Thanks Stephen. This is fixed now.
On Wed, Feb 12, 2025 at 08:12:51AM +1100, Stephen Rothwell wrote:
> Hi all,
>
> In commit
>
> a1bb25cad5ab ("iommu/amd: Expicitly enable CNTRL.EPHEn bit in resume path")
>
> Fixes tag
>
> Fixes: c4cb2311110 ("iommu/amd: Add support for enable/disable IOPF")
>
> has these problem(s):
>
> - SHA1 should be at least 12 digits long
> This can be fixed for 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
next prev parent reply other threads:[~2025-02-14 8:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-11 21:12 linux-next: Fixes tag needs some work in the iommu tree Stephen Rothwell
2025-02-14 8:13 ` Joerg Roedel [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-04-29 13:01 Stephen Rothwell
2022-05-04 8:33 ` Joerg Roedel
2021-04-15 21:51 Stephen Rothwell
2021-04-16 7:57 ` Dafna Hirschfeld
2020-06-30 21:01 Stephen Rothwell
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=Z677NjlRfHdOmdiy@8bytes.org \
--to=joro@8bytes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=vasant.hegde@amd.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 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.