public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Dave Airlie <airlied@linux•ie>,
	David Miller <davem@davemloft•net>,
	Networking <netdev@vger•kernel.org>
Cc: linux-next@vger•kernel.org, linux-kernel@vger•kernel.org,
	Jiri Pirko <jiri@mellanox•com>,
	Chris Wilson <chris@chris-wilson•co.uk>,
	Daniel Vetter <daniel.vetter@ffwll•ch>
Subject: linux-next: manual merge of the drm tree with the net-next tree
Date: Mon, 6 Feb 2017 12:46:27 +1100	[thread overview]
Message-ID: <20170206124627.6d7e2543@canb.auug.org.au> (raw)

Hi Dave,

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

  lib/Kconfig

between commit:

  44091d29f207 ("lib: Introduce priority array area manager")

from the net-next tree and commit:

  cf4a7207b1cb ("lib: Add a simple prime number generator")

from the drm 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 lib/Kconfig
index 5d644f180fe5,1788a1f50d28..000000000000
--- a/lib/Kconfig
+++ b/lib/Kconfig
@@@ -550,7 -550,11 +550,14 @@@ config STACKDEPO
  config SBITMAP
  	bool
  
 +config PARMAN
 +	tristate "parman"
 +
+ config PRIME_NUMBERS
+ 	tristate "Prime number generator"
+ 	default n
+ 	help
+ 	  Provides a helper module to generate prime numbers. Useful for writing
+ 	  test code, especially when checking multiplication and divison.
+ 
  endmenu

                 reply	other threads:[~2017-02-06  1:46 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=20170206124627.6d7e2543@canb.auug.org.au \
    --to=sfr@canb$(echo .)auug.org.au \
    --cc=airlied@linux$(echo .)ie \
    --cc=chris@chris-wilson$(echo .)co.uk \
    --cc=daniel.vetter@ffwll$(echo .)ch \
    --cc=davem@davemloft$(echo .)net \
    --cc=jiri@mellanox$(echo .)com \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=netdev@vger$(echo .)kernel.org \
    /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