archive mirror
 help / color / mirror / Atom feed
From: Andrea Arcangeli <>
To: Jeff Garzik <>
Cc: Linus Torvalds <>,
	Ingo Molnar <>,, Richard Henderson <>
Subject: Re: unregistered changes to the user<->kernel API
Date: Thu, 14 Jun 2001 19:44:20 +0200	[thread overview]
Message-ID: <20010614194419.A715@athlon.random> (raw)
In-Reply-To: <20010614191219.A30567@athlon.random> <>
In-Reply-To: <>; from on Thu, Jun 14, 2001 at 01:25:10PM -0400

On Thu, Jun 14, 2001 at 01:25:10PM -0400, Jeff Garzik wrote:
> They don't hurt but it's also a bad precedent - you don't want to add a
> ton of CONFIG_xxx to the Linus tree for stuff outside the Linus tree. 
> disagree with this patch.

If tux will ever be merged into mainline eventually I don't think
there's a value in defer such bit. Of course if tux will never get
merged then I totally agree with you.

> this conflicts with noone, so can wait for tux patch

same as above.

> ouch!   I would understand if this was inside CONFIG_TUX, but even so I
> would disagree until Tux is merged.

Then you may prefer to wait tux to be merged before merging the rest as
well, in the meantime 90% of the kernels running out there will show
such stuff out of /proc/stats (hopefully "the same stuff" which is why
I'm posting those patches in first place).


  reply	other threads:[~2001-06-14 17:45 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-14 17:12 unregistered changes to the user<->kernel API Andrea Arcangeli
2001-06-14 17:16 ` Andrea Arcangeli
2001-06-14 17:21   ` Andrea Arcangeli
2001-06-14 17:32     ` Richard Henderson
2001-06-14 17:47       ` Andrea Arcangeli
2001-06-14 18:16         ` Andrea Arcangeli
2001-06-14 18:17         ` Richard Henderson
2001-06-14 18:10       ` Alexander Viro
2001-06-14 17:25 ` Jeff Garzik
2001-06-14 17:44   ` Andrea Arcangeli [this message]
2001-06-14 17:52     ` Jeff Garzik
2001-06-14 18:03       ` Andrea Arcangeli
2001-06-14 18:11         ` Alan Cox
2001-06-14 18:27           ` Andrea Arcangeli
2001-06-14 21:43           ` Albert D. Cahalan

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20010614194419.A715@athlon.random \ \ \ \ \ \ \

* 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;
as well as URLs for NNTP newsgroup(s).