From: Neil Brown <neilb@suse.de>
To: Al Viro <viro@ZenIV.linux.org.uk>
Cc: Christoph Hellwig <hch@lst.de>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] Two patches for fs/super.c
Date: Wed, 24 Mar 2010 20:50:04 +1100 [thread overview]
Message-ID: <20100324205004.34d18940@notabene.brown> (raw)
In-Reply-To: <20100324092011.GO30031@ZenIV.linux.org.uk>
On Wed, 24 Mar 2010 09:20:11 +0000
Al Viro <viro@ZenIV.linux.org.uk> wrote:
> On Wed, Mar 24, 2010 at 04:12:23PM +1100, NeilBrown wrote:
> >
> > Two patches.
> >
> > The second removes S_BIAS which is unnecessary and so potentially
> > confusing.
> >
> > The first I found the need for while preparing the second patch. It
> > seems that get_active_super doesn't follow the pattern of all other
> > code that walks the super_blocks list.
>
> See #untested in vfs tree...
>
Ahhh, I see I've been beaten to it by 2 days... I should have posted that
patch months ago :-)
Thanks anyway.
NeilBrown
prev parent reply other threads:[~2010-03-24 9:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-24 5:12 [PATCH 0/2] Two patches for fs/super.c NeilBrown
2010-03-24 5:12 ` [PATCH 2/2] fs/super: remove S_BIAS NeilBrown
2010-03-24 5:12 ` [PATCH 1/2] VFS: use __put_super_and_need_restart in get_active_super NeilBrown
2010-03-24 9:20 ` [PATCH 0/2] Two patches for fs/super.c Al Viro
2010-03-24 9:50 ` Neil Brown [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=20100324205004.34d18940@notabene.brown \
--to=neilb@suse.de \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.