From: "Manfred Spraul" <manfred@colorfullife.com>
To: "Neil Brown" <neilb@cse.unsw.edu.au>
Cc: <linux-kernel@vger.kernel.org>, <linux-fsdevel@vger.kernel.org>
Subject: Re: [RFC] event cleanup, part 2
Date: Wed, 2 Jan 2002 10:19:05 +0100 [thread overview]
Message-ID: <002501c1936e$974d0f60$010411ac@local> (raw)
In-Reply-To: <3C32260E.CEADDF59@colorfullife.com> <15410.35800.154586.201540@notabene.cse.unsw.edu.au>
From: "Neil Brown" <neilb@cse.unsw.edu.au>
> On Tuesday January 1, manfred@colorfullife.com wrote:
> > Linus merged the first part of my patches that remove
> > 'event' into 2.5.2-pre3.
> >
> > Attached is the second patch.
> >
> > patch 1: remove all event users except readdir().
> > Merged.
>
> Not quite. ext2 and ext3 (At least) use event to set i_generation to
> a pseudo-random number, and that still seems to be so in 2.5.2-pre6.
> What do you plan to do with that usage of event?
> Possibly replacing it with net_random or similar would be fine.
>
I've replaced i_generation with a random number in ext2, that change
is part of 2.5.2-pre6.
I've sent the patch to ext3 to the maintainers.
--
Manfred
prev parent reply other threads:[~2002-01-02 9:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-01 21:11 [RFC] event cleanup, part 2 Manfred Spraul
2002-01-02 4:26 ` Neil Brown
2002-01-02 9:19 ` Manfred Spraul [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='002501c1936e$974d0f60$010411ac@local' \
--to=manfred@colorfullife.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@cse.unsw.edu.au \
/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.