From: Jens Axboe <axboe@kernel.dk>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Xen-devel <xen-devel@lists.xensource.com>,
Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 00/16] xen/blkfront: various bugfixes and patches for blkfront
Date: Tue, 20 Jul 2010 20:12:15 -0600 [thread overview]
Message-ID: <4C46577F.7050909@kernel.dk> (raw)
In-Reply-To: <cover.1279658231.git.jeremy.fitzhardinge@citrix.com>
On 07/20/2010 02:42 PM, Jeremy Fitzhardinge wrote:
> From: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com>
>
> Hi Jens,
>
> This series has various updates to blkfront, including:
> - support for dynamic device resizing
> - bugfixes for device hotplug
> - various races and bugs fixed
>
> It can be pulled from:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git upstream/blkfront
They don't apply cleanly to the for-2.6.36 branch, it fails at patch 2:
patching file drivers/block/xen-blkfront.c
Hunk #1 succeeded at 105 (offset 1 line).
Hunk #2 succeeded at 143 (offset 1 line).
Hunk #9 FAILED at 1080.
Hunk #10 succeeded at 1106 with fuzz 1 (offset 5 lines).
1 out of 10 hunks FAILED -- saving rejects to file drivers/block/xen-blkfront.c.rej
--
Jens Axboe
next prev parent reply other threads:[~2010-07-21 2:12 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1279658231.git.jeremy.fitzhardinge@citrix.com>
2010-07-20 20:42 ` [PATCH 01/16] xen: use less generic names in blkfront driver Jeremy Fitzhardinge
2010-07-20 20:42 ` [PATCH 02/16] blkfront: fixes for 'xm block-detach ... --force' Jeremy Fitzhardinge
2010-07-20 20:42 ` [PATCH 03/16] blkfront: don't access freed struct xenbus_device Jeremy Fitzhardinge
2010-07-20 20:42 ` [PATCH 04/16] xen/front: Propagate changed size of VBDs Jeremy Fitzhardinge
2010-07-20 20:42 ` [PATCH 05/16] xen/blkfront: avoid compiler warning from missing cases Jeremy Fitzhardinge
2010-07-20 20:42 ` [PATCH 06/16] xen/blkfront: revalidate after setting capacity Jeremy Fitzhardinge
2010-07-20 20:42 ` [PATCH 07/16] xenbus: Make xenbus_switch_state transactional Jeremy Fitzhardinge
2010-07-20 20:42 ` [PATCH 08/16] blkfront: Fix backtrace in del_gendisk Jeremy Fitzhardinge
2010-07-20 20:42 ` [PATCH 09/16] blkfront: Fix gendisk leak Jeremy Fitzhardinge
2010-07-20 20:42 ` [PATCH 10/16] blkfront: Clean up vbd release Jeremy Fitzhardinge
2010-07-20 20:42 ` [PATCH 11/16] blkfront: Lock blkfront_info when closing Jeremy Fitzhardinge
2010-07-20 20:42 ` [PATCH 12/16] blkfront: Fix blkfront backend switch race (bdev open) Jeremy Fitzhardinge
2010-07-20 20:42 ` [PATCH 13/16] blkfront: Fix blkfront backend switch race (bdev release) Jeremy Fitzhardinge
2010-07-20 20:42 ` [PATCH 14/16] blkfront: Lock blockfront_info during xbdev removal Jeremy Fitzhardinge
2010-07-20 20:42 ` [PATCH 15/16] blkfront: Remove obsolete info->users Jeremy Fitzhardinge
2010-07-20 20:42 ` [PATCH 16/16] blkfront: Klog the unclean release path Jeremy Fitzhardinge
2010-07-21 2:12 ` Jens Axboe [this message]
2010-07-21 5:03 ` [PATCH 00/16] xen/blkfront: various bugfixes and patches for blkfront Jeremy Fitzhardinge
2010-07-29 0:26 ` Jeremy Fitzhardinge
2010-08-02 17:45 ` Jeremy Fitzhardinge
2010-08-02 18:40 ` Jens Axboe
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=4C46577F.7050909@kernel.dk \
--to=axboe@kernel.dk \
--cc=jeremy.fitzhardinge@citrix.com \
--cc=jeremy@goop.org \
--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).