From: Chris Mason <mason@suse.com>
To: Claas Langbehn <claas@bigfoot.com>
Cc: reiserfs-list@namesys.com, linux-kernel@vger.kernel.org
Subject: Re: reiserfs patch for 2.4.0-final
Date: Fri, 05 Jan 2001 08:47:34 -0500 [thread overview]
Message-ID: <502300000.978702454@tiny> (raw)
In-Reply-To: <20010105140408.A2812@villariba.2y.net>
On Friday, January 05, 2001 02:04:08 PM +0100 Claas Langbehn
<claas@bigfoot.com> wrote:
> On Thu, Jan 04, 2001 at 04:52:49PM -0500, Chris Mason wrote:
>> This patch is meant to be applied on top of the reiserfs
>> 3.6.23 patch to get everything working in the new prerelease
>> kernels. The order is:
>>
>> untar linux-2.4.0-prerelease.tar.bz2
>> apply linux-2.4.0-test12-reiserfs-3.6.23.gz
>> apply this patch
>> apply the fs/super.c patch to make sure fsync_dev is called
>> when unmounting /. This was already sent to l-k, I'll send
>> to the reiserfs list as well.
>
> Is this still correct for the final 2.4.0-kernel ?
>
Yes
> Could someone create one single patch for the 2.4.0 ?
>
I put all the code into CVS, and Yura is making the official patch now.
-chris
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-05 13:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-04 21:52 reiserfs patch for 2.4.0-prerelease Chris Mason
2001-01-05 1:41 ` [reiserfs-list] " Ed Tomlinson
2001-01-06 16:52 ` [reiserfs-list] reiserfs patch for 2.4.0-prerelease (dbench runs) Ed Tomlinson
2001-01-05 13:04 ` reiserfs patch for 2.4.0-final Claas Langbehn
2001-01-05 13:47 ` Chris Mason [this message]
2001-01-05 15:56 ` Chris Evans
2001-01-05 16:54 ` Rik van Riel
2001-01-05 17:41 ` Chris Mason
2001-01-05 17:45 ` Admin Mailing Lists
2001-01-05 17:48 ` Rik van Riel
2001-01-05 18:44 ` Alan Cox
2001-01-05 18:52 ` Admin Mailing Lists
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=502300000.978702454@tiny \
--to=mason@suse.com \
--cc=claas@bigfoot.com \
--cc=linux-kernel@vger.kernel.org \
--cc=reiserfs-list@namesys.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