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


Groups > linux.kernel > #1362232 > unrolled thread

linux-next: manual merge of the rdma tree with Linus' tree

Started byStephen Rothwell <sfr@canb.auug.org.au>
First post2016-03-22 01:20 +0100
Last post2016-03-22 01:20 +0100
Articles 1 — 1 participant

Back to article view | Back to linux.kernel


Contents

  linux-next: manual merge of the rdma tree with Linus' tree Stephen Rothwell <sfr@canb.auug.org.au> - 2016-03-22 01:20 +0100

#1362232 — linux-next: manual merge of the rdma tree with Linus' tree

FromStephen Rothwell <sfr@canb.auug.org.au>
Date2016-03-22 01:20 +0100
Subjectlinux-next: manual merge of the rdma tree with Linus' tree
Message-ID<rfidc-4P4-7@gated-at.bofh.it>
Hi Doug,

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

  drivers/staging/rdma/hfi1/mad.c

between commits:

  a4fe1bc16411 ("staging: rdma: hfi1: Remove casts of pointer to same type")
  acc17d671c62 ("staging: rdma: hfi1: Remove unnecessary parantheses")

from Linus' tree and commit:

  58721b8f8c71 ("staging/rdma/hfi1: Remove unnecessary parentheses")

from the rdma tree.

I fixed it up (the result was like 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