From: Greg KH <greg@kroah.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Arnd Bergmann <arnd@arndb.de>, Tzung-Bi Shih <tzungbi@kernel.org>,
Chrome Platform <chrome-platform@lists.linux.dev>,
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 char-misc tree
Date: Mon, 8 Jan 2024 08:54:13 +0100 [thread overview]
Message-ID: <2024010805-stagnant-statute-ac41@gregkh> (raw)
In-Reply-To: <20240108140713.143f27e1@canb.auug.org.au>
On Mon, Jan 08, 2024 at 02:07:13PM +1100, Stephen Rothwell wrote:
> Hi all,
>
> The following commit is also in the chrome-platform-firmware tree as a
> different commit (but the same patch):
>
> f69583d32fcb ("firmware: coreboot_table: Convert to platform remove callback returning void")
>
> This is commit
>
> 09aeaabebdaf ("firmware: coreboot: Convert to platform remove callback returning void")
>
> in the chrome-platform-firmware tree.
Should be fine, thanks.
greg k-h
prev parent reply other threads:[~2024-01-08 7:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-08 3:07 linux-next: duplicate patch in the char-misc tree Stephen Rothwell
2024-01-08 7:54 ` Greg KH [this message]
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=2024010805-stagnant-statute-ac41@gregkh \
--to=greg@kroah.com \
--cc=arnd@arndb.de \
--cc=chrome-platform@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=tzungbi@kernel.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).