public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Greg KH <greg@kroah.com>, Arnd Bergmann <arnd@arndb.de>,
	Madhavan Srinivasan <maddy@linux.ibm.com>,
	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 patch in the char-misc tree
Date: Thu, 17 Jul 2025 15:37:33 +1000	[thread overview]
Message-ID: <20250717153733.068c3fc3@canb.auug.org.au> (raw)

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

Hi all,

The following commit is also in the powerpc tree as a different commit
(but the same patch):

  01c6d1df98cb ("misc: ocxl: Replace scnprintf() with sysfs_emit() in sysfs show functions")

This is commit

  e82fff08327e ("misc: ocxl: Replace scnprintf() with sysfs_emit() in sysfs show functions")

in the powerpc tree.

-- 
Cheers,
Stephen Rothwell

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

             reply	other threads:[~2025-07-17  5:37 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-17  5:37 Stephen Rothwell [this message]
2025-07-17  6:01 ` linux-next: duplicate patch in the char-misc tree Greg KH
  -- strict thread matches above, loose matches on Subject: below --
2025-07-18  7:41 Stephen Rothwell
2025-07-18  7:54 ` Greg KH
2025-02-24  5:00 Stephen Rothwell
2025-02-24  6:16 ` Greg KH
2024-06-06  2:34 Stephen Rothwell
2024-01-08  3:07 Stephen Rothwell
2024-01-08  7:54 ` Greg KH
2024-01-08  2:58 Stephen Rothwell
2024-01-08  7:37 ` Helge Deller
2024-01-08  7:46   ` 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=20250717153733.068c3fc3@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=maddy@linux.ibm.com \
    --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