From: Pasha Tatashin <pasha.tatashin@soleen.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Andrew Morton <akpm@linux-foundation.org>,
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 mm-hotfixes tree
Date: Tue, 12 Aug 2025 13:46:57 +0000 [thread overview]
Message-ID: <CA+CK2bA=thKfEuiFZ-Nmr1ZNALC7ZcKv5uPVy2RCgc-Jy96Now@mail.gmail.com> (raw)
In-Reply-To: <20250812164436.557c805f@canb.auug.org.au>
On Tue, Aug 12, 2025 at 6:44 AM Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> Hi all,
>
> In commit
>
> 25ee3c404f35 ("kho: mm: don't allow deferred struct page with KHO")
>
> Fixes tag
>
> Fixes: 990a950fe8fd ("kexec: add config option for KHO")
>
> has these problem(s):
>
> - Target SHA1 does not exist
>
> Maybe you meant
>
> Fixes: 4e1d010e3bda ("kexec: add config option for KHO")
Yes, this is the correct one. Thank you!
Andrew, do you want me to send a new patch version to update the commit log?
Pasha
>
> --
> Cheers,
> Stephen Rothwell
next prev parent reply other threads:[~2025-08-12 13:47 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-12 6:44 linux-next: Fixes tag needs some work in the mm-hotfixes tree Stephen Rothwell
2025-08-12 13:46 ` Pasha Tatashin [this message]
2025-08-12 20:12 ` Andrew Morton
-- strict thread matches above, loose matches on Subject: below --
2025-09-10 7:32 Stephen Rothwell
2025-08-26 9:08 Stephen Rothwell
2025-08-20 4:50 Stephen Rothwell
2024-10-07 20:44 Stephen Rothwell
2024-08-25 21:26 Stephen Rothwell
2024-08-04 21:17 Stephen Rothwell
2024-08-05 2:47 ` Muchun Song
2024-07-02 22:09 Stephen Rothwell
2023-11-29 20:43 Stephen Rothwell
2023-11-30 1:07 ` Baoquan He
2023-06-07 4:35 Stephen Rothwell
2022-08-07 21:19 Stephen Rothwell
2022-08-07 23:01 ` Peter Xu
2022-04-27 22: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='CA+CK2bA=thKfEuiFZ-Nmr1ZNALC7ZcKv5uPVy2RCgc-Jy96Now@mail.gmail.com' \
--to=pasha.tatashin@soleen.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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).