From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Peter Rosin <peda@axentia.se>, Greg KH <greg@kroah.com>,
Arnd Bergmann <arnd@arndb.de>
Cc: 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 mux tree
Date: Fri, 2 Jun 2023 13:31:48 +1000 [thread overview]
Message-ID: <20230602133148.1fc0b305@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 490 bytes --]
Hi all,
The following commits are also in the char-misc tree as different
commits (but the same patches):
213700a8b96f ("dt-bindings: ti-serdes-mux: Add defines for J784S4 SoC")
76ac787cd671 ("mux: mmio: drop obsolete dependency on COMPILE_TEST")
These are commits
8258d997b874 ("dt-bindings: ti-serdes-mux: Add defines for J784S4 SoC")
5ccf40288ca0 ("mux: mmio: drop obsolete dependency on COMPILE_TEST")
in the char-misc tree.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2023-06-02 3:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-02 3:31 Stephen Rothwell [this message]
2023-06-02 6:40 ` linux-next: duplicate patches in the mux tree Peter Rosin
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=20230602133148.1fc0b305@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=peda@axentia.se \
/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