mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@fb.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
	<linux-kernel@vger.kernel.org>, <xen-devel@lists.xensource.com>
Cc: <bob.liu@oracle.com>, <david.vrabel@citrix.com>
Subject: Re: for-4.8/drivers and Linus' tree + staging conflicts?
Date: Wed, 20 Jul 2016 17:48:37 -0600	[thread overview]
Message-ID: <4790e021-0695-abd4-9281-4f7342c79e59@fb.com> (raw)
In-Reply-To: <20160715161904.GA30284@char.us.oracle.com>

On 07/15/2016 10:19 AM, Konrad Rzeszutek Wilk wrote:
> Hey Jens,
>
> I have some patches for Xen block driver that are based on Linus's tree
> which has:
> 7b427a5     xen-blkfront: save uncompleted reqs in blkfront_resume()
>
> That particular patch conflicts with your for-4.8/driver branch.
>
> What I was wondering is if:
>
>  1) Do you want me to create a branh for you to pull in your
>     for-4.8/drivers that has the above patch (and a resolution)?
>     And along with that the rest of the patches I've for 4.8?

No, I don't want a lot of extra gunk.

>  2) Or if you are going rebase your 'for-4.8/drivers' branch
>    on top of v4.7-rc7 (which will pull in the above commit?)

Or that, I never rebase those branches.

>  3) Stash the patches I've in the Xen tip tree (which is
>    based on 4.7-rc7) for 4.8 with me putting your Ack on them?
>    See below log and the full diff.

We can do that, or I can stage them for post initial merge (essentially 
my for-linus, which I could base on 4.7-rc7 now). I'm fine with either.

-- 
Jens Axboe

  parent reply	other threads:[~2016-07-20 23:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-15 16:19 Konrad Rzeszutek Wilk
2016-07-20 19:41 ` Konrad Rzeszutek Wilk
2016-07-20 23:48 ` Jens Axboe [this message]
2016-07-21 14:06   ` Konrad Rzeszutek Wilk

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=4790e021-0695-abd4-9281-4f7342c79e59@fb.com \
    --to=axboe@fb.com \
    --cc=bob.liu@oracle.com \
    --cc=david.vrabel@citrix.com \
    --cc=konrad.wilk@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=xen-devel@lists.xensource.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

Powered by JetHome