linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alessio Igor Bogani <abogani@texware.it>
To: Christoph Hellwig <hch@infradead.org>
Cc: Alexander Viro <viro@zeniv.linux.org.uk>,
	Jonathan Corbet <corbet@lwn.net>,
	"Fr??d??ric Weisbecker" <fweisbec@gmail.com>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	LKML <linux-kernel@vger.kernel.org>,
	LFSDEV <linux-fsdevel@vger.kernel.org>,
	Matthew Wilcox <matthew@wil.cx>, Ingo Molnar <mingo@elte.hu>
Subject: Re: [PATCH vfs-2.6:for-next] vfs: remount_fs BKL pushdown
Date: Tue, 5 May 2009 21:39:38 +0200	[thread overview]
Message-ID: <63a49ef40905051239r61fe7f4cg6f24e13df30dc940@mail.gmail.com> (raw)
In-Reply-To: <20090505133743.GA663@infradead.org>

Dear Sir Hellwig,

2009/5/5 Christoph Hellwig <hch@infradead.org>:
> On Sat, Apr 25, 2009 at 04:23:49AM -0400, Christoph Hellwig wrote:
>> On Sat, Apr 25, 2009 at 10:09:05AM +0200, Alessio Igor Bogani wrote:
>> > Push BKL down into ->remount_fs()
>>
>> Please also push down lock_super, no need to have two locking changes in
>> this area just after another.
>
> Do you plan to do that respin?  I will need the lock_super pushdown for
> some sync work.  I can wait for you if you plan to submit it, otherwise
> I'll out it on my TODO list.

Apologize I have completely missed your first replay.

Let me two days for finish that task and for do build and boot tests.

Thanks!

Ciao,
Alessio
--
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:[~2009-05-05 19:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-25  8:09 [PATCH vfs-2.6:for-next] vfs: remount_fs BKL pushdown Alessio Igor Bogani
2009-04-25  8:23 ` Christoph Hellwig
2009-05-05 13:37   ` Christoph Hellwig
2009-05-05 19:39     ` Alessio Igor Bogani [this message]
2009-05-05 20:43       ` Christoph Hellwig
2009-05-06  3:51         ` Al Viro
2009-05-06  6:26           ` Christoph Hellwig
2009-05-06  6:48             ` Al Viro

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=63a49ef40905051239r61fe7f4cg6f24e13df30dc940@mail.gmail.com \
    --to=abogani@texware.it \
    --cc=a.p.zijlstra@chello.nl \
    --cc=corbet@lwn.net \
    --cc=fweisbec@gmail.com \
    --cc=hch@infradead.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matthew@wil.cx \
    --cc=mingo@elte.hu \
    --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;
as well as URLs for NNTP newsgroup(s).