Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1421577 > unrolled thread

linux-next: manual merge of the staging tree with the block tree

Started byStephen Rothwell <sfr@canb.auug.org.au>
First post2016-06-14 07:10 +0200
Last post2016-06-14 07:10 +0200
Articles 1 — 1 participant

Back to article view | Back to linux.kernel


Contents

  linux-next: manual merge of the staging tree with the block tree Stephen Rothwell <sfr@canb.auug.org.au> - 2016-06-14 07:10 +0200

#1421577 — linux-next: manual merge of the staging tree with the block tree

FromStephen Rothwell <sfr@canb.auug.org.au>
Date2016-06-14 07:10 +0200
Subjectlinux-next: manual merge of the staging tree with the block tree
Message-ID<rJOLT-e2-3@gated-at.bofh.it>
Hi Greg,

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

  drivers/staging/lustre/lustre/llite/lloop.c

between commit:

  95fe6c1a209e ("block, fs, mm, drivers: use bio set/get op accessors")

from the block tree and commit:

  67b1a24e883c ("staging: lustre: llite: remove lloop device")

from the staging tree.

I fixed it up (I removed the file) 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

[toc] | [standalone]


Back to top | Article view | linux.kernel


csiph-web