mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Martin Dalecki <dalecki@evision-ventures.com>
To: Alexander Viro <viro@math.psu.edu>
Cc: Daniel Phillips <phillips@bonn-fries.net>,
	linux-kernel@vger.kernel.org, ext2-devel@lists.sourceforge.net
Subject: Re: [PATCH] Son of Unbork (1 of 3)
Date: Mon, 25 Feb 2002 18:37:03 +0100	[thread overview]
Message-ID: <3C7A763F.7060203@evision-ventures.com> (raw)
In-Reply-To: <Pine.GSO.4.21.0202251224150.3162-100000@weyl.math.psu.edu>

Alexander Viro wrote:
> 
> On Sat, 23 Feb 2002, Daniel Phillips wrote:
> 
> 
>>This three patch set completes the removal of ext2-specific includes from 
>>fs.h.  When this is done, your kernel will compile a little faster, the Ext2 
>>source will be organized a little better, and then infamous fs.h super_block 
>>union will no longer hurt your eyes.  When every filesystem has been changed 
>>in a similar way, fs.h will finally be generic, in-memory super_blocks will be
>>somewhat smaller, and the kernel will compile quite a lot faster.  And peace
>>will come once more to Middle-Earth.  (I made that last part up.)
>>
>>Patch 1 adds alloc_super and destroy_super methods to struct file_system.  A 
>>
> 
> Vetoed.

Poczjemu? Why? It fits the concept of constructor and destructor - I'm 
just curious. I suppose some locking issues?


  parent reply	other threads:[~2002-02-25 17:39 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-23 18:12 Daniel Phillips
2002-02-25 17:24 ` Alexander Viro
2002-02-23 18:30   ` Daniel Phillips
2002-02-25 17:34   ` Alexander Viro
2002-02-23 19:13     ` Daniel Phillips
2002-02-25 18:28       ` Alexander Viro
2002-02-24  2:33         ` Daniel Phillips
2002-02-25 17:37   ` Martin Dalecki [this message]
2002-02-25 17:57   ` Alan Cox
2002-02-25 17:45     ` Alexander Viro

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=3C7A763F.7060203@evision-ventures.com \
    --to=dalecki@evision-ventures.com \
    --cc=ext2-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=phillips@bonn-fries.net \
    --cc=viro@math.psu.edu \
    /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

all inboxes | Powered by JetHome®