public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: David Miller <davem@davemloft.net>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	Philipp Zabel <p.zabel@pengutronix.de>
Cc: Daniel Machon <daniel.machon@microchip.com>,
	Herve Codina <herve.codina@bootlin.com>,
	Networking <netdev@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: manual merge of the net-next tree with the reset tree
Date: Fri, 1 Nov 2024 12:25:05 +1100	[thread overview]
Message-ID: <20241101122505.3eacd183@canb.auug.org.au> (raw)

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

Hi all,

Today's linux-next merge of the net-next tree got a conflict in:

  MAINTAINERS

between commit:

  86f134941a4b ("MAINTAINERS: Add the Microchip LAN966x PCI driver entry")

from the reset tree and commit:

  7280f01e79cc ("net: lan969x: add match data for lan969x")

from the net-next 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.

-- 
Cheers,
Stephen Rothwell

diff --cc MAINTAINERS
index a0cad73c28d0,c4027397286b..000000000000
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@@ -15179,12 -15091,13 +15185,19 @@@ S:	Maintaine
  F:	Documentation/devicetree/bindings/interrupt-controller/microchip,lan966x-oic.yaml
  F:	drivers/irqchip/irq-lan966x-oic.c
  
 +MICROCHIP LAN966X PCI DRIVER
 +M:	Herve Codina <herve.codina@bootlin.com>
 +S:	Maintained
 +F:	drivers/misc/lan966x_pci.c
 +F:	drivers/misc/lan966x_pci.dtso
 +
+ MICROCHIP LAN969X ETHERNET DRIVER
+ M:	Daniel Machon <daniel.machon@microchip.com>
+ M:	UNGLinuxDriver@microchip.com
+ L:	netdev@vger.kernel.org
+ S:	Maintained
+ F:	drivers/net/ethernet/microchip/lan969x/*
+ 
  MICROCHIP LCDFB DRIVER
  M:	Nicolas Ferre <nicolas.ferre@microchip.com>
  L:	linux-fbdev@vger.kernel.org

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

             reply	other threads:[~2024-11-01  1:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-01  1:25 Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-05-06  1:25 linux-next: manual merge of the net-next tree with the reset tree Stephen Rothwell
2025-05-30  1:03 ` 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=20241101122505.3eacd183@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=daniel.machon@microchip.com \
    --cc=davem@davemloft.net \
    --cc=herve.codina@bootlin.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=p.zabel@pengutronix.de \
    --cc=pabeni@redhat.com \
    /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