All of lore.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@fs.tum.de>
To: Dave Jones <davej@codemonkey.org.uk>,
	Matthew Wilcox <willy@debian.org>,
	linux-kernel@vger.kernel.org
Subject: Re: Dead & Dying interfaces
Date: Tue, 19 Nov 2002 20:01:47 +0100	[thread overview]
Message-ID: <20021119190146.GX11952@fs.tum.de> (raw)
In-Reply-To: <20021118175535.GD15318@suse.de>

On Mon, Nov 18, 2002 at 05:55:35PM +0000, Dave Jones wrote:
> On Fri, Nov 15, 2002 at 06:47:25PM +0000, Matthew Wilcox wrote:
> 
>  > This list is a combination of interfaces which have gone during 2.5 and
>  > interfaces that should go during 2.7.  Think of it as a `updating your
>  > driver/filesystem to sane code' guide.
> 
> Adding printk (KERN_DEBUG "Usage of check_region() is deprecated");
> to such interfaces may be an idea. For some of them, however it
> is probably a bad idea if the logs get flooded with zillions of warnings
> each boot.  Maybe just for the "We really should purge this crap next
> time" functions ?

What about a #warning? With a #warning everyone compiling this code sees
that there's something that needs updating but it doesn't flood the logs
of users (#warning was already used for linux/malloc.h in 2.4).

> 		Dave

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


  reply	other threads:[~2002-11-19 18:54 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-15 18:47 Dead & Dying interfaces Matthew Wilcox
2002-11-15 19:00 ` William Lee Irwin III
2002-11-16  2:49 ` Alan Cox
2002-11-17  0:41 ` Greg KH
2002-11-17  1:43   ` Alan Cox
2002-11-18 17:55 ` Dave Jones
2002-11-19 19:01   ` Adrian Bunk [this message]
2002-12-05  4:25 ` William Lee Irwin III

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=20021119190146.GX11952@fs.tum.de \
    --to=bunk@fs.tum.de \
    --cc=davej@codemonkey.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=willy@debian.org \
    /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.