All of lore.kernel.org
 help / color / mirror / Atom feed
From: Doug Ledford <dledford@redhat.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
	Jason Gunthorpe <jgg@mellanox.com>
Cc: Linux-Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Zhu Yanjun <yanjun.zhu@oracle.com>
Subject: Re: linux-next: manual merge of the rdma tree with the rdma-fixes tree
Date: Mon, 30 Apr 2018 20:55:35 -0400	[thread overview]
Message-ID: <1525136135.11756.94.camel@redhat.com> (raw)
In-Reply-To: <20180501101017.517b38af@canb.auug.org.au>

[-- Attachment #1: Type: text/plain, Size: 1164 bytes --]

On Tue, 2018-05-01 at 10:10 +1000, Stephen Rothwell wrote:
> Hi all,
> 
> Today's linux-next merge of the rdma tree got a conflict in:
> 
>   drivers/infiniband/sw/rxe/rxe_resp.c
> 
> between commit:
> 
>   9fd4350ba895 ("B/rxe: avoid double kfree_skb")
> 
> from the rdma-fixes tree and commit:
> 
>   2e47350789eb ("IB/rxe: optimize the function duplicate_request")
> 
> from the rdma tree.
> 
> I fixed it up (I think - 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.
> 

We will probably merge the for-rc branch into the for-next branch in the
next few days, at which point we will do the conflict resolution
ourselves and your need to carry anything should drop out.

-- 
Doug Ledford <dledford@redhat.com>
    GPG KeyID: B826A3330E572FDD
    Key fingerprint = AE6B 1BDA 122B 23B4 265B  1274 B826 A333 0E57 2FDD

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2018-05-01  0:55 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-01  0:10 linux-next: manual merge of the rdma tree with the rdma-fixes tree Stephen Rothwell
2018-05-01  0:55 ` Doug Ledford [this message]
2018-05-02 10:22   ` Leon Romanovsky
2018-05-02 14:00     ` Doug Ledford
2018-05-02 17:50       ` Jason Gunthorpe
  -- strict thread matches above, loose matches on Subject: below --
2025-03-06  1:37 Stephen Rothwell
2025-03-06 10:24 ` Zhu Yanjun
2025-03-06 11:35   ` Zhu Yanjun
     [not found] ` <4d66668a-ff8e-48f6-a5e3-98ada08c5037@linux.dev>
2025-03-06 20:33   ` Stephen Rothwell
2023-09-28  1:38 Stephen Rothwell
2023-09-28  9:59 ` Leon Romanovsky
2022-01-06  0:44 Stephen Rothwell
2021-09-30  1:35 Stephen Rothwell
2021-10-01 13:52 ` Jason Gunthorpe
2019-08-23  2:22 Stephen Rothwell
2019-08-23 15:02 ` Jason Gunthorpe
2018-07-10  1:17 Stephen Rothwell
2018-07-10  5:19 ` Leon Romanovsky
2018-06-27  0:07 Stephen Rothwell
2018-06-27  5:50 ` Leon Romanovsky
2018-03-22  0:45 Stephen Rothwell
2018-01-17  1:51 Stephen Rothwell
2018-01-17  1:55 ` Stephen Rothwell
2018-01-17  3:03   ` Jason Gunthorpe

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=1525136135.11756.94.camel@redhat.com \
    --to=dledford@redhat.com \
    --cc=jgg@mellanox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=yanjun.zhu@oracle.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.