public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Chris Mason <mason@suse.com>
Cc: linux-kernel@vger.kernel.org, marcelo@conectiva.com.br
Subject: Re: [PATCH] write_super is not for syncing (take 3)
Date: Mon, 5 Aug 2002 18:37:04 +0100	[thread overview]
Message-ID: <20020805183704.A18612@infradead.org> (raw)
In-Reply-To: <1028568893.1805.270.camel@tiny>; from mason@suse.com on Mon, Aug 05, 2002 at 01:34:53PM -0400

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?


  reply	other threads:[~2002-08-05 17:33 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 [this message]
2002-08-05 17:48   ` Chris Mason
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=20020805183704.A18612@infradead.org \
    --to=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo@conectiva.com.br \
    --cc=mason@suse.com \
    /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