From: Tejun Heo <tj@kernel.org>
To: Greg KH <gregkh@suse.de>
Cc: Jens Axboe <jens.axboe@oracle.com>,
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 16:58:40 +0200 [thread overview]
Message-ID: <48B2C8A0.4070100@kernel.org> (raw)
In-Reply-To: <20080825144714.GA20813@suse.de>
Greg KH wrote:
>> 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?
Ah.. okay, it's fixed in Linus's tree. Anyways, what do you think about
the new iterator?
> 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?
It's probably something which no one really cares but it's not difficult
to fix and having the behavior changed for 2.6.27 and reverted in 28
isn't too nice. I'll send a patch.
Thanks.
--
tejun
next prev parent reply other threads:[~2008-08-25 15:00 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
2008-08-25 14:58 ` Tejun Heo [this message]
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=48B2C8A0.4070100@kernel.org \
--to=tj@kernel.org \
--cc=draconux@gmail.com \
--cc=gregkh@suse.de \
--cc=jens.axboe@oracle.com \
--cc=linux-kernel@vger.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