From: Greg KH <gregkh@suse.de>
To: Tejun Heo <tj@kernel.org>, Jens Axboe <jens.axboe@oracle.com>
Cc: Abdel Benamrouche <draconux@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCHSET 1/3 blk-for-2.6.28] block: misc fixes and improvements
Date: Mon, 25 Aug 2008 07:47:14 -0700 [thread overview]
Message-ID: <20080825144714.GA20813@suse.de> (raw)
In-Reply-To: <1219655740-11672-1-git-send-email-tj@kernel.org>
On Mon, Aug 25, 2008 at 06:15:35PM +0900, Tejun Heo wrote:
> Hello,
>
> This patchset contains the following five patches containing misc
> fixes and improvements.
>
> 0001-block-fix-partition-info-printouts.patch
> 0002-block-don-t-grab-block_class_lock-unnecessarily.patch
> 0003-block-use-class_dev_iterator-instead-of-class_for_e.patch
> 0004-block-allow-deleting-zero-length-partition.patch
> 0005-block-update-add_partition-error-handling.patch
>
> Recent block_class iteration updates 5c6f35c5..27f3025 introduced a
> few bugs and trivial user visible behavior change. 0001-0003 update
> those issues and simplify related code using new class iterator.
The bugs should now be fixed in Linus's tree due to a fix from Kay,
right?
The user visable behavior change, I missed that, sorry, that is a
regression, do you think it's a big deal to fix in 2.6.27?
> 0004 fixes deletion of zero sized partitions.
>
> d805dda4 tried to fix error handling path in add_partition() but had a
> few problems. 0005 fixes those and moves busy partition check into
> add_partition().
>
> This patchset is against
>
> blk-for-2.6.28 (9abd7c437c02e7448fb1d2d3cfc0b9c1ab77cf2d)
> + [1] klist-dont-iterate-over-deleted-entries
> + [2] use-klist-for-class-device-list-and-implement-iterator
>
> and available in the following git tree.
>
> http://git.kernel.org/?p=linux/kernel/git/tj/misc.git;a=shortlog;h=block-misc-fixes
> git://git.kernel.org/pub/scm/linux/kernel/git/tj/misc.git block-misc-fixes
>
> with the following combined diffstat
I have no problem taking all of these patches as I did this original
work and don't want to burden Jens with this. Also, I'd like to work
off of the klist changes and class changes as that can be used in other
work that I want to do in the driver core.
Jens any objection to me taking them? Do you also have changes in this
area that this needs to be merged with?
thanks,
greg k-h
next prev parent reply other threads:[~2008-08-25 14:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-25 9:15 [PATCHSET 1/3 blk-for-2.6.28] block: misc fixes and improvements Tejun Heo
2008-08-25 9:15 ` [PATCH] block: fix partition info printouts Tejun Heo
2008-08-25 9:15 ` [PATCH] block: don't grab block_class_lock unnecessarily Tejun Heo
2008-08-25 9:15 ` [PATCH] block: use class_dev_iterator instead of class_for_each_device() Tejun Heo
2008-08-25 9:15 ` [PATCH] block: allow deleting zero length partition Tejun Heo
2008-08-25 9:15 ` [PATCH] block: update add_partition() error handling Tejun Heo
2008-08-25 10:23 ` [PATCHSET 1/3 blk-for-2.6.28] block: misc fixes and improvements Tejun Heo
2008-08-25 14:47 ` Greg KH [this message]
2008-08-25 14:58 ` Tejun Heo
2008-08-25 14:59 ` Tejun Heo
2008-08-25 14:58 ` Jens Axboe
2008-08-25 21:42 ` Greg KH
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=20080825144714.GA20813@suse.de \
--to=gregkh@suse.de \
--cc=draconux@gmail.com \
--cc=jens.axboe@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tj@kernel.org \
/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