linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg@mellanox.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Leon Romanovsky <leon@kernel.org>,
	Doug Ledford <dledford@redhat.com>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Yishai Hadas <yishaih@mellanox.com>,
	David Miller <davem@davemloft.net>,
	Networking <netdev@vger.kernel.org>
Subject: Re: linux-next: manual merge of the mlx5-next tree with the rdma tree
Date: Mon, 8 Jul 2019 16:09:03 +0000	[thread overview]
Message-ID: <20190708160858.GI23966@mellanox.com> (raw)
In-Reply-To: <20190708132837.5ccb36ed@canb.auug.org.au>

On Mon, Jul 08, 2019 at 01:28:37PM +1000, Stephen Rothwell wrote:
> Hi all,
> 
> On Thu, 4 Jul 2019 12:47:38 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> >
> > Hi all,
> > 
> > Today's linux-next merge of the mlx5-next tree got a conflict in:
> > 
> >   drivers/infiniband/hw/mlx5/cq.c
> > 
> > between commit:
> > 
> >   e39afe3d6dbd ("RDMA: Convert CQ allocations to be under core responsibility")
> > 
> > from the rdma tree and commit:
> > 
> >   38164b771947 ("net/mlx5: mlx5_core_create_cq() enhancements")
> > 
> > from the mlx5-next 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.
> > 
> 
> This is now a conflict between the net-next tree and the rdma tree.

You'll see the mlx5-next merge with rdma tomorrow that will take care
of this

Thanks,
Jason

  reply	other threads:[~2019-07-08 16:09 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-04  2:47 linux-next: manual merge of the mlx5-next tree with the rdma tree Stephen Rothwell
2019-07-04  6:27 ` Leon Romanovsky
2019-07-08  3:28 ` Stephen Rothwell
2019-07-08 16:09   ` Jason Gunthorpe [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-05-14  2:59 Stephen Rothwell
2020-05-14  5:54 ` Leon Romanovsky
2019-04-30  3:58 Stephen Rothwell
2019-05-06  4:01 ` Stephen Rothwell
2019-05-06  4:13   ` Leon Romanovsky
2019-05-09  1:07   ` Stephen Rothwell
2018-12-05  1:07 Stephen Rothwell
2018-12-05  1:33 ` Doug Ledford
2018-12-05  2:10   ` Stephen Rothwell
2018-12-05  6:30     ` Leon Romanovsky
2018-11-21  0:04 Stephen Rothwell
2018-11-21  7:16 ` Leon Romanovsky

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190708160858.GI23966@mellanox.com \
    --to=jgg@mellanox.com \
    --cc=davem@davemloft.net \
    --cc=dledford@redhat.com \
    --cc=leon@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=yishaih@mellanox.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).