public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Vineet Gupta <vgupta@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
	Andrew Morton <akpm@linux-foundation.org>,
	Vineet Gupta <vgupta@kernel.org>
Cc: Baoquan He <bhe@redhat.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: manual merge of the mm-stable tree with the arc-current tree
Date: Mon, 21 Aug 2023 18:31:53 -0700	[thread overview]
Message-ID: <8f8c8da7-b5a4-63b4-96fb-31a53721b5f2@kernel.org> (raw)
In-Reply-To: <20230822082841.7948474d@canb.auug.org.au>



On 8/21/23 15:28, Stephen Rothwell wrote:
> Hi all,
>
> Today's linux-next merge of the mm-stable tree got a conflict in:
>
>    arch/arc/Kconfig
>
> between commit:
>
>    f798f91e7f5f ("ARC: uaccess: use optimized generic __strnlen_user/__strncpy_from_user")
>
> from the arc-current tree and commit:
>
>    06dfae39d200 ("arc: mm: convert to GENERIC_IOREMAP")
>
> from the mm-stable tree.
>
> BTW, if the "select GENERIC_IOREMAP" had been put in its (alphabetical)
> proper place, this conflict would not have occurred ...
>
> 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.
>

Thx a bunch Stephen.

-Vineet

      reply	other threads:[~2023-08-22  1:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-21 22:28 linux-next: manual merge of the mm-stable tree with the arc-current tree Stephen Rothwell
2023-08-22  1:31 ` Vineet Gupta [this message]

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=8f8c8da7-b5a4-63b4-96fb-31a53721b5f2@kernel.org \
    --to=vgupta@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=bhe@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.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