From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Jens Axboe <axboe@fb.com>
Cc: linux-kernel@vger.kernel.org, xen-devel@lists.xensource.com,
bob.liu@oracle.com, david.vrabel@citrix.com
Subject: Re: for-4.8/drivers and Linus' tree + staging conflicts?
Date: Thu, 21 Jul 2016 10:06:19 -0400 [thread overview]
Message-ID: <20160721140619.GI11916@char.us.oracle.com> (raw)
In-Reply-To: <4790e021-0695-abd4-9281-4f7342c79e59@fb.com>
On Wed, Jul 20, 2016 at 05:48:37PM -0600, Jens Axboe wrote:
> 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.
OK, lets go with this one and we will stick them in xen-tip.
Thanks Jens!
>
> --
> Jens Axboe
>
prev parent reply other threads:[~2016-07-21 14:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-15 16:19 for-4.8/drivers and Linus' tree + staging conflicts? Konrad Rzeszutek Wilk
2016-07-20 19:41 ` Konrad Rzeszutek Wilk
2016-07-20 23:48 ` Jens Axboe
2016-07-21 14:06 ` Konrad Rzeszutek Wilk [this message]
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=20160721140619.GI11916@char.us.oracle.com \
--to=konrad.wilk@oracle.com \
--cc=axboe@fb.com \
--cc=bob.liu@oracle.com \
--cc=david.vrabel@citrix.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;
as well as URLs for NNTP newsgroup(s).