public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: 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: linux-next: manual merge of the mm-stable tree with the arc-current tree
Date: Tue, 22 Aug 2023 08:28:41 +1000	[thread overview]
Message-ID: <20230822082841.7948474d@canb.auug.org.au> (raw)

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

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.

-- 
Cheers,
Stephen Rothwell

diff --cc arch/arc/Kconfig
index c92bacc1ff4c,6f4995ad9873..000000000000
--- a/arch/arc/Kconfig
+++ b/arch/arc/Kconfig
@@@ -21,6 -21,6 +21,7 @@@ config AR
  	select DMA_DIRECT_REMAP
  	select GENERIC_ATOMIC64 if !ISA_ARCV2 || !(ARC_HAS_LL64 && ARC_HAS_LLSC)
  	# for now, we don't need GENERIC_IRQ_PROBE, CONFIG_GENERIC_IRQ_CHIP
++	select GENERIC_IOREMAP
  	select GENERIC_IRQ_SHOW
  	select GENERIC_PCI_IOMAP
  	select GENERIC_PENDING_IRQ if SMP

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

             reply	other threads:[~2023-08-21 22:29 UTC|newest]

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

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=20230822082841.7948474d@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=akpm@linux-foundation.org \
    --cc=bhe@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=vgupta@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox