From: Hans de Goede <hdegoede@redhat•com>
To: Stephen Rothwell <sfr@canb•auug.org.au>,
Mark Gross <markgross@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 drivers-x86 tree
Date: Wed, 20 Nov 2024 15:02:33 +0100 [thread overview]
Message-ID: <4ad0f4f7-417d-4668-a0d8-ceef13814483@redhat.com> (raw)
In-Reply-To: <20241119080658.7d0866a0@canb.auug.org.au>
Hi,
On 18-Nov-24 10:06 PM, Stephen Rothwell wrote:
> Hi all,
>
> In commit
>
> c6a2b4fcec5f ("platform/x86: p2sb: Cache correct PCI bar for P2SB on Gemini Lake")
>
> Fixes tag
>
> Fixes: 2841631a0365 ("platform/x86: p2sb: Allow p2sb_bar() calls during PCI device probe")
>
> has these problem(s):
>
> - Target SHA1 does not exist
>
> Maybe you meant
>
> Fixes: b28ff7a7c324 ("platform/x86: p2sb: Allow p2sb_bar() calls during PCI device probe")
Sorry I don't know where that wrong hash came from.
The suggested replacement hash is correct.
But I see that Ilpo has already tagged things and send out
a pull-request so I'm afraid it is too late to fix this one.
Regards,
Hans
next prev parent reply other threads:[~2024-11-20 14:02 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-18 21:06 linux-next: Fixes tag needs some work in the drivers-x86 tree Stephen Rothwell
2024-11-20 14:02 ` Hans de Goede [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-03-01 21:17 Stephen Rothwell
2022-03-02 11:17 ` Hans de Goede
2021-11-01 21:37 Stephen Rothwell
2021-11-02 10:28 ` Hans de Goede
2021-08-10 22:16 Stephen Rothwell
2021-08-12 7:40 ` Hans de Goede
2021-03-08 6:06 Stephen Rothwell
2021-03-08 10:36 ` Hans de Goede
2020-11-29 17:43 Stephen Rothwell
2020-11-30 7:43 ` Hans de Goede
2020-11-30 7:58 ` Stephen Rothwell
2020-04-23 22:53 Stephen Rothwell
2020-04-24 9:46 ` Andy Shevchenko
2019-06-11 21:43 Stephen Rothwell
2019-04-16 21:33 Stephen Rothwell
2019-02-06 22:57 Stephen Rothwell
[not found] ` <38152c55-c2c1-c89f-2751-0ef0d40fcba9@linux.intel.com>
2019-02-07 15:55 ` Andy Shevchenko
2019-02-13 15:15 ` Bhardwaj, Rajneesh
2019-02-21 0:40 ` Darren Hart
2019-02-21 13:36 ` Andy Shevchenko
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=4ad0f4f7-417d-4668-a0d8-ceef13814483@redhat.com \
--to=hdegoede@redhat$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=markgross@kernel$(echo .)org \
--cc=sfr@canb$(echo .)auug.org.au \
/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