All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
	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 nvmem tree
Date: Mon, 6 May 2024 15:42:26 +1000	[thread overview]
Message-ID: <20240506154226.5442be65@canb.auug.org.au> (raw)

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

Hi all,

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

  9e29a1dba59b ("nvmem: meson-mx-efuse: Remove nvmem_device from efuse struct")
  2ce7240c076f ("dt-bindings: nvmem: Add compatible for SC8280XP")
  af868167a709 ("dt-bindings: nvmem: qcom,spmi-sdam: update maintainer")
  e5630036dab1 ("dt-bindings: nvmem: Add compatible for sm8450, sm8550 and sm8650")
  04075398ec4f ("nvmem: lpc18xx_eeprom: Convert to platform remove callback returning void")
  ea8f9ec2bbb7 ("nvmem: core: switch to use device_add_groups()")
  fbd0d725d4fa ("nvmem: sprd: fix module autoloading")
  fc7d05b8e427 ("nvmem: sc27xx: fix module autoloading")
  3575d48e5d2f ("nvmem: layouts: sl28vpd: drop driver owner initialization")
  995b22c48ed0 ("nvmem: layouts: onie-tlv: drop driver owner initialization")
  e428f11ae8fb ("nvmem: layouts: store owner from modules with nvmem_layout_driver_register()")

These are commits

  2a1ad6b75292 ("nvmem: meson-mx-efuse: Remove nvmem_device from efuse struct")
  a5888ae5b3c3 ("dt-bindings: nvmem: Add compatible for SC8280XP")
  dc5d4043510b ("dt-bindings: nvmem: qcom,spmi-sdam: update maintainer")
  e2c7d6e02382 ("dt-bindings: nvmem: Add compatible for sm8450, sm8550 and sm8650")
  693d2f629962 ("nvmem: lpc18xx_eeprom: Convert to platform remove callback returning void")
  8d8fc146dd7a ("nvmem: core: switch to use device_add_groups()")
  154c1ec943e3 ("nvmem: sprd: fix module autoloading")
  dc3d88ade857 ("nvmem: sc27xx: fix module autoloading")
  23fd602f2195 ("nvmem: layouts: sl28vpd: drop driver owner initialization")
  21833338eccb ("nvmem: layouts: onie-tlv: drop driver owner initialization")
  6d0ca4a2a7e2 ("nvmem: layouts: store owner from modules with nvmem_layout_driver_register()")

in the char-misc tree.

-- 
Cheers,
Stephen Rothwell

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

             reply	other threads:[~2024-05-06  5:42 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-06  5:42 Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-12-18  5:12 linux-next: duplicate patches in the nvmem tree Stephen Rothwell
2023-12-18 10:26 ` Greg KH
2023-12-18 10:38   ` Srinivas Kandagatla
2023-12-18 10:30 ` Srinivas Kandagatla
2023-10-25  4:23 Stephen Rothwell
2023-10-17  4:07 Stephen Rothwell
2023-10-17  5:45 ` Srinivas Kandagatla
2023-09-25 22:34 Stephen Rothwell
2023-09-26  6:03 ` Srinivas Kandagatla
2023-09-04 22:04 Stephen Rothwell
2023-07-03 21:58 Stephen Rothwell
2023-05-08  1:00 Stephen Rothwell
2023-02-05 21:32 Stephen Rothwell
2023-03-05 23:51 ` Stephen Rothwell

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=20240506154226.5442be65@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=srinivas.kandagatla@linaro.org \
    /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.