linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Wang <wangyun@linux.vnet.ibm.com>
To: LKML <linux-kernel@vger.kernel.org>, linux-raid@vger.kernel.org
Cc: neilb@suse.de, "paulmck@linux.vnet.ibm.com" <paulmck@linux.vnet.ibm.com>
Subject: Re: [PATCH 1/3] raid: replace	list_for_each_continue_rcu with new interface
Date: Mon, 10 Sep 2012 16:30:11 +0800	[thread overview]
Message-ID: <504DA513.2060004@linux.vnet.ibm.com> (raw)
In-Reply-To: <5036D00F.2040009@linux.vnet.ibm.com>

On 08/24/2012 08:51 AM, Michael Wang wrote:
> On 08/17/2012 12:33 PM, Michael Wang wrote:
>> From: Michael Wang <wangyun@linux.vnet.ibm.com>
>>
>> This patch replaces list_for_each_continue_rcu() with
>> list_for_each_entry_continue_rcu() to save a few lines
>> of code and allow removing list_for_each_continue_rcu().
>>
> 
> Hi, Neil
> 
> Could I get some comments on this patch?

Hi, Neil

Could I get some comments?

And please forgive and warn me if this patch has came to the wrong
place...I get the address from get_maintainer.

Regards,
Michael Wang

> 
> Regards,
> Michael Wang
> 
>> Signed-off-by: Michael Wang <wangyun@linux.vnet.ibm.com>
>> ---
>>  drivers/md/bitmap.c |    9 +++------
>>  1 files changed, 3 insertions(+), 6 deletions(-)
>>
>> diff --git a/drivers/md/bitmap.c b/drivers/md/bitmap.c
>> index 15dbe03..b160828 100644
>> --- a/drivers/md/bitmap.c
>> +++ b/drivers/md/bitmap.c
>> @@ -163,20 +163,17 @@ static struct md_rdev *next_active_rdev(struct md_rdev *rdev, struct mddev *mdde
>>  	 * As devices are only added or removed when raid_disk is < 0 and
>>  	 * nr_pending is 0 and In_sync is clear, the entries we return will
>>  	 * still be in the same position on the list when we re-enter
>> -	 * list_for_each_continue_rcu.
>> +	 * list_for_each_entry_continue_rcu.
>>  	 */
>> -	struct list_head *pos;
>>  	rcu_read_lock();
>>  	if (rdev == NULL)
>>  		/* start at the beginning */
>> -		pos = &mddev->disks;
>> +		rdev = list_entry_rcu(&mddev->disks, struct md_rdev, same_set);
>>  	else {
>>  		/* release the previous rdev and start from there. */
>>  		rdev_dec_pending(rdev, mddev);
>> -		pos = &rdev->same_set;
>>  	}
>> -	list_for_each_continue_rcu(pos, &mddev->disks) {
>> -		rdev = list_entry(pos, struct md_rdev, same_set);
>> +	list_for_each_entry_continue_rcu(rdev, &mddev->disks, same_set) {
>>  		if (rdev->raid_disk >= 0 &&
>>  		    !test_bit(Faulty, &rdev->flags)) {
>>  			/* this is a usable devices */
>>
> 

  reply	other threads:[~2012-09-10  8:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <502CB924.10200@linux.vnet.ibm.com>
2012-08-17  4:33 ` [PATCH 1/3] raid: replace list_for_each_continue_rcu with new interface Michael Wang
2012-08-20 23:41   ` Paul E. McKenney
2012-08-24  0:51   ` Michael Wang
2012-09-10  8:30     ` Michael Wang [this message]
2012-09-11  6:21       ` NeilBrown
2012-09-11  6:27         ` Michael Wang
2012-09-11 16:28           ` Paul E. McKenney

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=504DA513.2060004@linux.vnet.ibm.com \
    --to=wangyun@linux.vnet.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=neilb@suse.de \
    --cc=paulmck@linux.vnet.ibm.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).