public inbox for linux-next@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>,
	Andrew Morton <akpm@linux-foundation•org>
Cc: Networking <netdev@vger•kernel.org>,
	Alexey Makhalov <alexey.makhalov@broadcom•com>,
	Krzysztof Kozlowski <krzysztof.kozlowski@linaro•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 tree with the mm-hotfixes tree
Date: Fri, 5 Apr 2024 08:22:47 +1100	[thread overview]
Message-ID: <20240405082247.177638cf@canb.auug.org.au> (raw)

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

Hi all,

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

  MAINTAINERS

between commit:

  ba74dd4f0460 ("MAINTAINERS: change vmware.com addresses to broadcom.com")

from the mm-hotfixes tree and commit:

  fa84513997e9 ("ptp: MAINTAINERS: drop Jeff Sipek")

from the net tree.

I fixed it up (I just used the former version) 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

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

                 reply	other threads:[~2024-04-04 21:22 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20240405082247.177638cf@canb.auug.org.au \
    --to=sfr@canb$(echo .)auug.org.au \
    --cc=akpm@linux-foundation$(echo .)org \
    --cc=alexey.makhalov@broadcom$(echo .)com \
    --cc=davem@davemloft$(echo .)net \
    --cc=krzysztof.kozlowski@linaro$(echo .)org \
    --cc=kuba@kernel$(echo .)org \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=netdev@vger$(echo .)kernel.org \
    --cc=pabeni@redhat$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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