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 13:38:51 -0800	[thread overview]
Message-ID: <3E0F6B6B.2FCEC917@digeo.com> (raw)
In-Reply-To: 20021229215554.A11360@lst.de

Christoph Hellwig wrote:
> 
> Rename the deprecated attribute to __deprecated to make it obvious
> this is something special and to avoid namespace clashes.
> 
> Mark more functionality deprecated:
> 
>  - sleep_on & friends

Please do not make sleep_on() generate a warning.  Unless you intend
to do the same to lock_kernel().

ext3 uses sleep_on().  It is perfectly safe.   Weaning ext3 off lock_kernel()
is a large, delicate and thus-far undesigned body of work.  I've been
working on other stuff and it is quite unlikely that ext3 locking will
be redesigned in the 2.5 timeframe.

>  - old module interfaces
> 
> This gives quite a lot warnings, I'll start to fix the ones in
> core code and stuff I maintain now..

Sounds like pointless churn to me.  How about we fix some real stuff and get
this kernel out the door before we all die?

  reply	other threads:[~2002-12-29 21:30 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 [this message]
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
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=3E0F6B6B.2FCEC917@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