* linux-next: manual merge of the nvmem tree with the char-misc.current tree
@ 2026-07-31 15:10 Mark Brown
2026-08-03 8:46 ` Greg Kroah-Hartman
0 siblings, 1 reply; 2+ messages in thread
From: Mark Brown @ 2026-07-31 15:10 UTC (permalink / raw)
To: Srinivas Kandagatla
Cc: Greg Kroah-Hartman, Linux Kernel Mailing List,
Linux Next Mailing List, Mathieu Dubois-Briand
[-- Attachment #1: Type: text/plain, Size: 1293 bytes --]
Hi all,
Today's linux-next merge of the nvmem tree got a conflict in:
drivers/nvmem/layouts/Makefile
between commit:
b5be879519291 ("nvmem: layouts: Add fixed-layout driver")
from the char-misc.current tree and commits:
c00ca6cc2fc96 ("nvmem: layouts: Add fixed-layout driver")
eeb4218f73b55 ("nvmem: layouts: Make the fixed-layout driver optional")
from the nvmem tree.
I fixed it up (see below) and can carry the fix as necessary. This
is now fixed as far as linux-next is concerned, but any non trivial
conflicts should be mentioned to your upstream maintainer when your tree
is submitted for merging. You may also want to consider cooperating
with the maintainer of the conflicting tree to minimise any particularly
complex conflicts.
diff --combined drivers/nvmem/layouts/Makefile
index dd6c6c70b1a92,9da790a9dde9e..0000000000000
--- a/drivers/nvmem/layouts/Makefile
+++ b/drivers/nvmem/layouts/Makefile
@@@ -3,7 -3,7 +3,7 @@@
# Makefile for nvmem layouts.
#
- obj-$(CONFIG_NVMEM_LAYOUTS) += fixed-layout.o
+ obj-$(CONFIG_NVMEM_LAYOUT_FIXED_LAYOUT) += fixed-layout.o
obj-$(CONFIG_NVMEM_LAYOUT_SL28_VPD) += sl28vpd.o
obj-$(CONFIG_NVMEM_LAYOUT_ONIE_TLV) += onie-tlv.o
obj-$(CONFIG_NVMEM_LAYOUT_U_BOOT_ENV) += u-boot-env.o
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: linux-next: manual merge of the nvmem tree with the char-misc.current tree
2026-07-31 15:10 linux-next: manual merge of the nvmem tree with the char-misc.current tree Mark Brown
@ 2026-08-03 8:46 ` Greg Kroah-Hartman
0 siblings, 0 replies; 2+ messages in thread
From: Greg Kroah-Hartman @ 2026-08-03 8:46 UTC (permalink / raw)
To: Mark Brown
Cc: Srinivas Kandagatla, Linux Kernel Mailing List,
Linux Next Mailing List, Mathieu Dubois-Briand
On Fri, Jul 31, 2026 at 04:10:38PM +0100, Mark Brown wrote:
> Hi all,
>
> Today's linux-next merge of the nvmem tree got a conflict in:
>
> drivers/nvmem/layouts/Makefile
>
> between commit:
>
> b5be879519291 ("nvmem: layouts: Add fixed-layout driver")
>
> from the char-misc.current tree and commits:
>
> c00ca6cc2fc96 ("nvmem: layouts: Add fixed-layout driver")
> eeb4218f73b55 ("nvmem: layouts: Make the fixed-layout driver optional")
>
> from the nvmem tree.
>
> I fixed it up (see below) and can carry the fix as necessary. This
> is now fixed as far as linux-next is concerned, but any non trivial
> conflicts should be mentioned to your upstream maintainer when your tree
> is submitted for merging. You may also want to consider cooperating
> with the maintainer of the conflicting tree to minimise any particularly
> complex conflicts.
>
> diff --combined drivers/nvmem/layouts/Makefile
> index dd6c6c70b1a92,9da790a9dde9e..0000000000000
> --- a/drivers/nvmem/layouts/Makefile
> +++ b/drivers/nvmem/layouts/Makefile
> @@@ -3,7 -3,7 +3,7 @@@
> # Makefile for nvmem layouts.
> #
>
> - obj-$(CONFIG_NVMEM_LAYOUTS) += fixed-layout.o
> + obj-$(CONFIG_NVMEM_LAYOUT_FIXED_LAYOUT) += fixed-layout.o
> obj-$(CONFIG_NVMEM_LAYOUT_SL28_VPD) += sl28vpd.o
> obj-$(CONFIG_NVMEM_LAYOUT_ONIE_TLV) += onie-tlv.o
> obj-$(CONFIG_NVMEM_LAYOUT_U_BOOT_ENV) += u-boot-env.o
This all should be handled now, hopefully, as the nvmem patches were
sent to me from the nvmem tree to be merged into it.
thanks,
greg k-h
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2026-08-03 8:47 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-07-31 15:10 linux-next: manual merge of the nvmem tree with the char-misc.current tree Mark Brown
2026-08-03 8:46 ` Greg Kroah-Hartman
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox