mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jan Blunck <jblunck@suse.de>
To: Phillip Lougher <phillip@lougher.demon.co.uk>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	matthew@wil.cx, viro@zeniv.linux.org.uk
Subject: Re: BKL: Remove BKL from Squashfs
Date: Wed, 11 Nov 2009 16:16:16 +0100	[thread overview]
Message-ID: <20091111151616.GF21750@bolzano.suse.de> (raw)
In-Reply-To: <4AF9DD24.8060501@lougher.demon.co.uk>

On Tue, Nov 10, Phillip Lougher wrote:

> Phillip Lougher wrote:
> 
> >This patch was prompted by Jan Blunck's "Push down BKL to the 
> >filesystems" patch
> >series, where he firstly pushes the BKL down to individual filesystems
> >(even if they don't need it) , and then successively removes them
> >(on a one patch per filesystem basis) in later patches.
> >
> >The patch should be reviewed in the context that it is intended for Jan's
> >BKL removal patch series.
> >
> 
> Jan and/or Matthew,
> 
> Can you please ACK this patch, and say whether you're going to
> add it to your BKL patch series? (I'm happy for it to go through
> there, rather than my Squashfs tree).
> 
> After reviewing your patches, it seems to me that the BKL isn't
> needed in Squashfs.  You removed it from 23 filesystems because
> it's not protecting any shared state,  on that basis it isn't needed
> needed in Squashfs either.

Yes, I'll do this through my patch series. I'll rework the series a bit and
will repost it soon.

Thanks,
	Jan

-- 
Jan Blunck <jblunck@suse.de>

      reply	other threads:[~2009-11-11 15:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-03 15:15 Phillip Lougher
2009-11-10 20:15 ` Andrew Morton
2009-11-10 21:11   ` Phillip Lougher
2009-11-10 21:37     ` Phillip Lougher
2009-11-11 15:16       ` Jan Blunck [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=20091111151616.GF21750@bolzano.suse.de \
    --to=jblunck@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matthew@wil.cx \
    --cc=phillip@lougher.demon.co.uk \
    --cc=viro@zeniv.linux.org.uk \
    /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

all inboxes | Powered by JetHome®