From: Leon Romanovsky <leon@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Doug Ledford <dledford@redhat.com>,
Jason Gunthorpe <jgg@mellanox.com>,
David Miller <davem@davemloft.net>,
Networking <netdev@vger.kernel.org>,
Linux-Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Eran Ben Elisha <eranbe@mellanox.com>,
Saeed Mahameed <saeedm@mellanox.com>,
Eugenia Emantayev <eugenia@mellanox.com>,
Mark Bloch <markb@mellanox.com>
Subject: Re: linux-next: manual merge of the rdma tree with the net tree
Date: Mon, 15 Jan 2018 14:24:11 +0200 [thread overview]
Message-ID: <20180115122411.GA15760@mtr-leonro.local> (raw)
In-Reply-To: <20180115115321.1d1abc11@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 1067 bytes --]
On Mon, Jan 15, 2018 at 11:53:21AM +1100, Stephen Rothwell wrote:
> Hi all,
>
> Today's linux-next merge of the rdma tree got a conflict in:
>
> drivers/infiniband/hw/mlx5/main.c
>
> between commits:
>
> 8978cc921fc7 ("{net,ib}/mlx5: Don't disable local loopback multicast traffic when needed")
> 72f36be06138 ("net/mlx5: Fix mlx5_get_uars_page to return error code")
>
> from the net tree and commits:
>
> 16c1975f1032 ("IB/mlx5: Create profile infrastructure to add and remove stages")
> c8b8992446a9 ("IB/mlx5: Move loopback initialization to the corresponding stage")
>
> from the rdma 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.
>
> --
> Cheers,
> Stephen Rothwell
>
Thanks, Stephen.
It looks right to me.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-01-15 12:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-15 0:53 linux-next: manual merge of the rdma tree with the net tree Stephen Rothwell
2018-01-15 12:24 ` Leon Romanovsky [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-12-17 0:08 Stephen Rothwell
2018-12-17 21:24 ` Saeed Mahameed
2022-05-19 1:35 Stephen Rothwell
2022-05-19 4:03 ` Saeed Mahameed
2022-05-19 17:48 ` Jakub Kicinski
2022-05-20 22:16 ` Saeed Mahameed
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=20180115122411.GA15760@mtr-leonro.local \
--to=leon@kernel.org \
--cc=davem@davemloft.net \
--cc=dledford@redhat.com \
--cc=eranbe@mellanox.com \
--cc=eugenia@mellanox.com \
--cc=jgg@mellanox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=markb@mellanox.com \
--cc=netdev@vger.kernel.org \
--cc=saeedm@mellanox.com \
--cc=sfr@canb.auug.org.au \
/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