From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Greg KH <greg@kroah.com>, Arnd Bergmann <arnd@arndb.de>,
Michael Ellerman <mpe@ellerman.id.au>
Cc: PowerPC <linuxppc-dev@lists.ozlabs.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: duplicate patches in the char-misc tree
Date: Wed, 29 Nov 2023 12:24:05 +1100 [thread overview]
Message-ID: <20231129122405.27a5e54a@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 826 bytes --]
Hi all,
The following commits are also in the powerpc tree as different commits
(but the same patches):
bc1183a63057 ("misc: ocxl: main: Remove unnecessary ‘0’ values from rc")
29eb0dc7bd1e ("misc: ocxl: link: Remove unnecessary (void*) conversions")
0e425d703c30 ("misc: ocxl: afu_irq: Remove unnecessary (void*) conversions")
62df29a542f9 ("misc: ocxl: context: Remove unnecessary (void*) conversions")
These are commits
29685ea5754f ("misc: ocxl: main: Remove unnecessary ‘0’ values from rc")
220f3ced8e42 ("misc: ocxl: link: Remove unnecessary (void*) conversions")
84ba5d3675e2 ("misc: ocxl: afu_irq: Remove unnecessary (void*) conversions")
82d30723d58f ("misc: ocxl: context: Remove unnecessary (void*) conversions")
in the powerpc tree.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2023-11-29 1:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-29 1:24 Stephen Rothwell [this message]
2023-11-29 9:26 ` linux-next: duplicate patches in the char-misc tree Greg KH
-- strict thread matches above, loose matches on Subject: below --
2024-01-08 3:02 Stephen Rothwell
2024-01-08 7:54 ` 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 7:54 ` Linus Walleij
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=20231129122405.27a5e54a@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=arnd@arndb.de \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.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).