linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Francis Moreau <francis.moro@gmail.com>
To: Jan Kara <jack@suse.cz>
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] ext2_free_inode(): remove useless call to brelse()
Date: Tue, 13 Apr 2010 11:02:56 +0200	[thread overview]
Message-ID: <m2i38b2ab8a1004130202y4034a010wce3f44d0e8118fcc@mail.gmail.com> (raw)
In-Reply-To: <20100408100112.GC20488@quack.suse.cz>

On Thu, Apr 8, 2010 at 12:01 PM, Jan Kara <jack@suse.cz> wrote:
> On Thu 08-04-10 11:57:48, Jan Kara wrote:
>> On Fri 26-03-10 14:07:00, Francis Moreau wrote:
>> > This patch removes a useless call to brelse(bitmap_bh) since at that
>> > point bitmap_bh is NULL.
>> >
>> > It also converts the last brelse(bitmap_bh) into a __brelse(bitmap_bh)
>> > since at that point bitmap_bh is no more NULL.
>>   The cleanup looks fine. Only I'd use normal brelse instead of __brelse
>> at the end. The compiler should figure out itself that the check is
>> unnecessary (if not, the cost of extra test is negligible in that path
>> anyway) and you don't have to think twice when looking at the function.
>> Also you don't have to initialize bitmap_bh to NULL after your cleanups.
>> So I've taken your patch with these two minor changes.
>  Just for reference, here's the patch I currently carry.
>

ok,


thanks
-- 
Francis
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      reply	other threads:[~2010-04-13  9:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-26 13:07 [PATCH] ext2_free_inode(): remove useless call to brelse() Francis Moreau
2010-04-08  9:57 ` Jan Kara
2010-04-08 10:01   ` Jan Kara
2010-04-13  9:02     ` Francis Moreau [this message]

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=m2i38b2ab8a1004130202y4034a010wce3f44d0e8118fcc@mail.gmail.com \
    --to=francis.moro@gmail.com \
    --cc=jack@suse.cz \
    --cc=linux-fsdevel@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;
as well as URLs for NNTP newsgroup(s).