linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Greg KH <greg@kroah.com>, Arnd Bergmann <arnd@arndb.de>,
	Olof Johansson <olof@lixom.net>
Cc: Linus Walleij <linus.walleij@linaro.org>,
	ARM <linux-arm-kernel@lists.infradead.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: Fri, 2 Jun 2023 13:26:54 +1000	[thread overview]
Message-ID: <20230602132654.4497f896@canb.auug.org.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 490 bytes --]

Hi all,

The following commits are also in the arm-soc tree as different
commits (but the same patches):

  b866e7e7f995 ("misc: sram: Generate unique names for subpools")
  ca3222ac4477 ("dt-bindings: sram: Add compatible for ST-Ericsson U8500 eSRAM")

These are commits

  21e5a2d10c8f ("misc: sram: Generate unique names for subpools")
  38bd22dac71e ("dt-bindings: sram: Add compatible for ST-Ericsson U8500 eSRAM")

in the arm-soc tree.

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

             reply	other threads:[~2023-06-02  3:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-02  3:26 Stephen Rothwell [this message]
2023-06-02  7:54 ` linux-next: duplicate patches in the char-misc tree Linus Walleij
2023-06-02  8:01   ` Greg KH
2023-08-07  5:44 Stephen Rothwell
2023-08-07  6:40 ` Greg KH
2023-11-29  1:24 Stephen Rothwell
2023-11-29  9:26 ` Greg KH
2024-01-08  3:02 Stephen Rothwell
2024-01-08  7:54 ` 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=20230602132654.4497f896@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=arnd@arndb.de \
    --cc=greg@kroah.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=olof@lixom.net \
    /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).