linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* linux-next: manual merge of the cisco tree with the vfs tree
@ 2018-10-02  6:29 Stephen Rothwell
  2019-01-14 22:33 ` Stephen Rothwell
  0 siblings, 1 reply; 4+ messages in thread
From: Stephen Rothwell @ 2018-10-02  6:29 UTC (permalink / raw)
  To: Daniel Walker, Al Viro
  Cc: Linux-Next Mailing List, Linux Kernel Mailing List, David Howells

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

Hi Daniel,

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

  arch/x86/kernel/setup.c

between commit:

  dcf8001d292b ("vfs: Suppress MS_* flag defs within the kernel unless explicitly enabled")

from the vfs tree and commit:

  2c070709ea75 ("This updates the x86 code to use the CONFIG_GENERIC_CMDLINE")

from the cisco 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 arch/x86/kernel/setup.c
index e493202bf265,ee109f490b22..000000000000
--- a/arch/x86/kernel/setup.c
+++ b/arch/x86/kernel/setup.c
@@@ -51,7 -51,7 +51,8 @@@
  #include <linux/kvm_para.h>
  #include <linux/dma-contiguous.h>
  #include <xen/xen.h>
 +#include <uapi/linux/mount.h>
+ #include <linux/cmdline.h>
  
  #include <linux/errno.h>
  #include <linux/kernel.h>

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

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: linux-next: manual merge of the cisco tree with the vfs tree
  2018-10-02  6:29 linux-next: manual merge of the cisco tree with the vfs tree Stephen Rothwell
@ 2019-01-14 22:33 ` Stephen Rothwell
  2019-01-14 22:54   ` Daniel Walker
  0 siblings, 1 reply; 4+ messages in thread
From: Stephen Rothwell @ 2019-01-14 22:33 UTC (permalink / raw)
  To: Daniel Walker
  Cc: Al Viro, Linux-Next Mailing List, Linux Kernel Mailing List,
	David Howells

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

Hi Daniel,

On Tue, 2 Oct 2018 16:29:23 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> Today's linux-next merge of the cisco tree got a conflict in:
> 
>   arch/x86/kernel/setup.c
> 
> between commit:
> 
>   dcf8001d292b ("vfs: Suppress MS_* flag defs within the kernel unless explicitly enabled")
> 
> from the vfs tree and commit:
> 
>   2c070709ea75 ("This updates the x86 code to use the CONFIG_GENERIC_CMDLINE")
> 
> from the cisco 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 arch/x86/kernel/setup.c
> index e493202bf265,ee109f490b22..000000000000
> --- a/arch/x86/kernel/setup.c
> +++ b/arch/x86/kernel/setup.c
> @@@ -51,7 -51,7 +51,8 @@@
>   #include <linux/kvm_para.h>
>   #include <linux/dma-contiguous.h>
>   #include <xen/xen.h>
>  +#include <uapi/linux/mount.h>
> + #include <linux/cmdline.h>
>   
>   #include <linux/errno.h>
>   #include <linux/kernel.h>

This is now a conflict between the cicso tree and Linus' tree.

-- 
Cheers,
Stephen Rothwell

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

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: linux-next: manual merge of the cisco tree with the vfs tree
  2019-01-14 22:33 ` Stephen Rothwell
@ 2019-01-14 22:54   ` Daniel Walker
  2019-01-15  0:18     ` Stephen Rothwell
  0 siblings, 1 reply; 4+ messages in thread
From: Daniel Walker @ 2019-01-14 22:54 UTC (permalink / raw)
  To: Stephen Rothwell
  Cc: Al Viro, Linux-Next Mailing List, Linux Kernel Mailing List,
	David Howells

On Tue, Jan 15, 2019 at 09:33:30AM +1100, Stephen Rothwell wrote:
> Hi Daniel,
> 
> On Tue, 2 Oct 2018 16:29:23 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> >
> > Today's linux-next merge of the cisco tree got a conflict in:
> > 
> >   arch/x86/kernel/setup.c
> > 
> > between commit:
> > 
> >   dcf8001d292b ("vfs: Suppress MS_* flag defs within the kernel unless explicitly enabled")
> > 
> > from the vfs tree and commit:
> > 
> >   2c070709ea75 ("This updates the x86 code to use the CONFIG_GENERIC_CMDLINE")
> > 
> > from the cisco 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 arch/x86/kernel/setup.c
> > index e493202bf265,ee109f490b22..000000000000
> > --- a/arch/x86/kernel/setup.c
> > +++ b/arch/x86/kernel/setup.c
> > @@@ -51,7 -51,7 +51,8 @@@
> >   #include <linux/kvm_para.h>
> >   #include <linux/dma-contiguous.h>
> >   #include <xen/xen.h>
> >  +#include <uapi/linux/mount.h>
> > + #include <linux/cmdline.h>
> >   
> >   #include <linux/errno.h>
> >   #include <linux/kernel.h>
> 
> This is now a conflict between the cicso tree and Linus' tree.

I did a rebase after your original made this. I'm not sure it's needed any
longer. However, I was planning to rebase my tree again on top of the latest
Linus tree. How would you like to proceed ?

Daniel

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: linux-next: manual merge of the cisco tree with the vfs tree
  2019-01-14 22:54   ` Daniel Walker
@ 2019-01-15  0:18     ` Stephen Rothwell
  0 siblings, 0 replies; 4+ messages in thread
From: Stephen Rothwell @ 2019-01-15  0:18 UTC (permalink / raw)
  To: Daniel Walker
  Cc: Al Viro, Linux-Next Mailing List, Linux Kernel Mailing List,
	David Howells

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

Hi Daniel,

On Mon, 14 Jan 2019 14:54:12 -0800 Daniel Walker <dwalker@fifo99.com> wrote:
>
> I did a rebase after your original made this. I'm not sure it's needed any
> longer. However, I was planning to rebase my tree again on top of the latest
> Linus tree. How would you like to proceed ?

I still get the conflict when I merge your tree, but it is not such a
bit conflict that it warrants rebasing your tree to get rid of it.  It
will be sorted out easily enough when Linus merges your tree.

-- 
Cheers,
Stephen Rothwell

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

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2019-01-15  0:18 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2018-10-02  6:29 linux-next: manual merge of the cisco tree with the vfs tree Stephen Rothwell
2019-01-14 22:33 ` Stephen Rothwell
2019-01-14 22:54   ` Daniel Walker
2019-01-15  0:18     ` Stephen Rothwell

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).