[lkml]   [2019]   [Feb]   [21]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: linux-next: build failure after merge of the xarray tree
On Thu, Feb 21, 2019 at 11:47:16PM +1100, Stephen Rothwell wrote:
> Hi Jason,
> On Wed, 13 Feb 2019 22:09:36 +0000 Jason Gunthorpe <> wrote:
> >
> > I personally think it is not good to put major logic changes in merge
> > commits, so I would prefer the #2 approach for this case.
> These are not difficult merge fixes or logic changes.

That comment was directed at Matt's correct suggestion to use
alloc_cyclic, this same suggestion applies to this conflict as well.

The mechanical change of the args is not so bad for a merge commit.

> > SFR's tree is just a reference. Who ever takes care to resolve these
> > conflicts has to manually do the fixing up. If you do send your tree
> > early I will fix it up as part of prepping the RDMA tree PR. Otherwise
> > you will have to fix it.
> Neither of you need to fix it ...

Not quite, I always re-do and verify all your merge resolutions and
send them to Linus as both a raw diff and as an actual merge commit
for him to reference. This way these things are checked in multiple

It is difficult to run this flow if we don't have an agreed order of
trees, as producing the resolutions for an unmerged tree is not so
straight forward.


 \ /
  Last update: 2019-02-21 18:41    [W:0.078 / U:0.256 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site