public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@digeo.com>
To: Christoph Hellwig <hch@lst.de>
Cc: torvalds@transmeta.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] more deprectation bits
Date: Sun, 29 Dec 2002 14:26:12 -0800	[thread overview]
Message-ID: <3E0F7684.6D07D4FB@digeo.com> (raw)
In-Reply-To: 20021229225843.A12122@lst.de

Christoph Hellwig wrote:
> 
> On Sun, Dec 29, 2002 at 01:55:48PM -0800, Andrew Morton wrote:
> > > Even if it's safe in that particular case, most code in the kernel runs
> > > without BKL.  This patch just makes the deprication of sleep_on
> > > explicit.
> >
> > This would be more appropriate:
> 
> I don't think so.  As you said before sleep_on is perfectly fine for
> the small part of code still covered by BKL, so we should not impose
> any runtime overhead (i.e. warnings) but rather remind at compile time.
> 
> That's what's so nice with the gcc extension (and you won't see it
> anyway as long as you stay at egcs 1.1 :))

Others will.  It will result in developers being distracted into "fixing"
non-bugs.  It will introduce risk and it will delay the release of the
2.6 kernel.

Please concentrate on things which *matter*.  Focus on getting this piece
of software into a deliverable state and do not be distracted into futzing
about with stuff which clearly was not addressed at the appropriate time.

  reply	other threads:[~2002-12-29 22:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-29 20:55 [PATCH] more deprectation bits Christoph Hellwig
2002-12-29 21:38 ` Andrew Morton
2002-12-29 21:47   ` Christoph Hellwig
2002-12-29 21:55     ` Andrew Morton
2002-12-29 21:58       ` Christoph Hellwig
2002-12-29 22:26         ` Andrew Morton [this message]
2002-12-29 22:40           ` John Bradford
2002-12-31  2:30       ` Bill Davidsen

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=3E0F7684.6D07D4FB@digeo.com \
    --to=akpm@digeo.com \
    --cc=hch@lst.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.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