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


Groups > linux.kernel > #1664397 > unrolled thread

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

Started byStephen Rothwell <sfr@canb.auug.org.au>
First post2017-06-13 06:40 +0200
Last post2017-06-13 06:40 +0200
Articles 1 — 1 participant

Back to article view | Back to linux.kernel


Contents

  linux-next: manual merge of the md tree with the block tree Stephen Rothwell <sfr@canb.auug.org.au> - 2017-06-13 06:40 +0200

#1664397 — linux-next: manual merge of the md tree with the block tree

FromStephen Rothwell <sfr@canb.auug.org.au>
Date2017-06-13 06:40 +0200
Subjectlinux-next: manual merge of the md tree with the block tree
Message-ID<tRLMu-3kB-17@gated-at.bofh.it>
Hi Shaohua,

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

  drivers/md/raid5.c

between commit:

  4e4cbee93d56 ("block: switch bios to blk_status_t")

from the block tree and commit:

  66a8066d55fd ("md: simplify code with bio_io_error")

from the md tree.

I fixed it up (the latter removed code updated by the former) 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