From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Daniel Stodden <daniel.stodden@citrix.com>
Cc: ksrinivasan <ksrinivasan@novell.com>,
Xen <xen-devel@lists.xensource.com>,
Jan Beulich <JBeulich@novell.com>
Subject: Re: [PATCH 00 of 10] blkfront pvops updates
Date: Thu, 29 Apr 2010 14:10:52 -0700 [thread overview]
Message-ID: <4BD9F5DC.4040208@goop.org> (raw)
In-Reply-To: <1272574715.25447.34.camel@agari.van.xensource.com>
On 04/29/2010 01:58 PM, Daniel Stodden wrote:
> Ah, that's where the previous stuff ended up. I thought those probably
> just got dropped.
>
I thought the changes in these patches looked somewhat familiar.
> Let's just scratch those. It's been months, so if they didn't make it
> back then, they won't need to complicate stuff now either.
>
> So I should probably merge with xen/frontend. If those matter, they must
> be on some branch which matters. Which one is it? I thought the one
> which matters is xen/master? Is it xen/next?
>
The flow of changes is (ideally):
<topic branch> -> xen/next -> xen/stable*
where "->" is merged into.
I'm going to clean things up a bit by re-creating xen/blkfront with the
changes from xen/frontend. If you rebase your patches onto xen/frontend
then I should be able to easily incorporate them into that cleanup.
Sorry for the mixup.
Thanks,
J
next prev parent reply other threads:[~2010-04-29 21:10 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-29 2:19 [PATCH 00 of 10] blkfront pvops updates Daniel Stodden
2010-04-29 2:19 ` [PATCH 01 of 10] xenbus: Make xenbus_switch_state transactional (again) Daniel Stodden
2010-04-29 2:19 ` [PATCH 02 of 10] blkfront: Fix backtrace in del_gendisk Daniel Stodden
2010-04-29 2:19 ` [PATCH 03 of 10] blkfront: Fix gendisk leak Daniel Stodden
2010-04-29 2:19 ` [PATCH 04 of 10] blkfront: Clean up vbd release Daniel Stodden
2010-04-29 2:19 ` [PATCH 05 of 10] blkfront: Lock blkfront_info when closing Daniel Stodden
2010-04-29 2:19 ` [PATCH 06 of 10] blkfront: Fix blkfront backend switch race (bdev open) Daniel Stodden
2010-04-29 2:19 ` [PATCH 07 of 10] blkfront: Fix blkfront backend switch race (bdev release) Daniel Stodden
2010-04-29 2:19 ` [PATCH 08 of 10] blkfront: Lock blockfront_info during xbdev removal Daniel Stodden
2010-04-29 2:19 ` [PATCH 09 of 10] blkfront: Remove obsolete info->users Daniel Stodden
2010-04-29 2:19 ` [PATCH 10 of 10] blkfront: Klog the unclean release path Daniel Stodden
2010-04-29 19:50 ` [PATCH 00 of 10] blkfront pvops updates Jeremy Fitzhardinge
2010-04-29 20:11 ` Daniel Stodden
2010-04-29 20:58 ` Daniel Stodden
2010-04-29 21:10 ` Jeremy Fitzhardinge [this message]
2010-04-29 21:28 ` Daniel Stodden
2010-04-29 21:36 ` Jeremy Fitzhardinge
2010-04-29 23:05 ` Daniel Stodden
2010-04-30 18:01 ` Jeremy Fitzhardinge
2010-04-30 18:13 ` Jeremy Fitzhardinge
2010-04-30 20:12 ` Daniel Stodden
2010-04-30 11:34 ` Daniel Stodden
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=4BD9F5DC.4040208@goop.org \
--to=jeremy@goop.org \
--cc=JBeulich@novell.com \
--cc=daniel.stodden@citrix.com \
--cc=ksrinivasan@novell.com \
--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 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.