From: Chris Mason <mason@suse.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: linux-kernel@vger.kernel.org, marcelo@conectiva.com.br, alan@redhat.com
Subject: Re: [PATCH] write_super is not for syncing (take 3)
Date: 05 Aug 2002 13:48:43 -0400 [thread overview]
Message-ID: <1028569723.1759.275.camel@tiny> (raw)
In-Reply-To: <20020805183704.A18612@infradead.org>
On Mon, 2002-08-05 at 13:37, Christoph Hellwig wrote:
> On Mon, Aug 05, 2002 at 01:34:53PM -0400, Chris Mason wrote:
> > Below are just the hunks that change VFS code, against 2.4.19-final.
> > The reiserfs bits will come once this gets accepted. Please review and
> > throw something blunt at me if you don't want this in the kernel.
>
> Could you please get that tested in 2.5 or -ac first?
It is being tested in the suse kernel now. Alan, if you want it, I'll
rediff against 2.4.19-ac.
-chris
next prev parent reply other threads:[~2002-08-05 17:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-05 17:34 [PATCH] write_super is not for syncing (take 3) Chris Mason
2002-08-05 17:37 ` Christoph Hellwig
2002-08-05 17:48 ` Chris Mason [this message]
2002-08-05 20:32 ` Alan Cox
2002-08-09 12:34 ` Daniel Phillips
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=1028569723.1759.275.camel@tiny \
--to=mason@suse.com \
--cc=alan@redhat.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
/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