From: Greg KH <greg@kroah.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Arnd Bergmann <arnd@arndb.de>,
Sudeep Holla <sudeep.holla@arm.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: duplicate patches in the char-misc tree
Date: Mon, 8 Jan 2024 08:54:03 +0100 [thread overview]
Message-ID: <2024010856-bottle-tipoff-21d5@gregkh> (raw)
In-Reply-To: <20240108140254.6def2dc7@canb.auug.org.au>
On Mon, Jan 08, 2024 at 02:02:54PM +1100, Stephen Rothwell wrote:
> Hi all,
>
> The following commits are also in the scmi tree as different commits
> (but the same patches):
>
> 259566503782 ("firmware: arm_scpi: Convert to platform remove callback returning void")
> 927e11300d8e ("firmware: arm_scmi: Convert to platform remove callback returning void")
>
> These are commits
>
> 8b12056b2cbf ("firmware: arm_scpi: Convert to platform remove callback returning void")
> 66926739f592 ("firmware: arm_scmi: Convert to platform remove callback returning void")
>
> in the scmi tree.
Should be fine, thanks.
greg k-h
next prev parent reply other threads:[~2024-01-08 7:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-08 3:02 linux-next: duplicate patches in the char-misc tree Stephen Rothwell
2024-01-08 7:54 ` Greg KH [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-11-29 1:24 Stephen Rothwell
2023-11-29 1:24 ` Stephen Rothwell
2023-11-29 9:26 ` Greg KH
2023-11-29 9:26 ` Greg KH
2023-08-07 5:44 Stephen Rothwell
2023-08-07 6:40 ` Greg KH
2023-06-02 3:26 Stephen Rothwell
2023-06-02 3:26 ` Stephen Rothwell
2023-06-02 7:54 ` Linus Walleij
2023-06-02 7:54 ` Linus Walleij
2023-06-02 8:01 ` Greg KH
2023-06-02 8:01 ` Greg KH
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=2024010856-bottle-tipoff-21d5@gregkh \
--to=greg@kroah.com \
--cc=arnd@arndb.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=sudeep.holla@arm.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.