From: Mike Rapoport <rppt@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: duplicate patch in the memblock tree
Date: Sat, 11 Nov 2023 08:54:03 -0500 [thread overview]
Message-ID: <20231111135403.GA6696@kernel.org> (raw)
In-Reply-To: <20231109085024.3de5b700@canb.auug.org.au>
Hi Stephen,
On Thu, Nov 09, 2023 at 08:50:24AM +1100, Stephen Rothwell wrote:
> Hi all,
>
> The following commit is also in Linus Torvalds' tree as a different commit
> (but the same patch):
>
> 0f5e4adb608c ("memblock: report failures when memblock_can_resize is not set")
>
> This is commit
>
> e96c6b8f212a ("memblock: report failures when memblock_can_resize is not set")
>
> in Linus' tree.
It looks like I forgot to push for-next with e96c6b8f212a after rebasing it :(
> --
> Cheers,
> Stephen Rothwell
--
Sincerely yours,
Mike.
next prev parent reply other threads:[~2023-11-11 13:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-08 21:50 linux-next: duplicate patch in the memblock tree Stephen Rothwell
2023-11-11 13:54 ` Mike Rapoport [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-04-28 11:04 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=20231111135403.GA6696@kernel.org \
--to=rppt@kernel.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