linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Willy Tarreau <w@1wt.eu>
To: Dave Jones <davej@redhat.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Andi Kleen <andi@firstfloor.org>,
	"Robert P. J. Day" <rpjday@mindspring.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Adrian Bunk <bunk@stusta.de>
Subject: Re: [PATCH] Delete obsolete RAW driver feature.
Date: Thu, 22 Mar 2007 05:45:40 +0100	[thread overview]
Message-ID: <20070322044540.GA32191@1wt.eu> (raw)
In-Reply-To: <20070322041751.GB17159@redhat.com>

On Thu, Mar 22, 2007 at 12:17:51AM -0400, Dave Jones wrote:
> On Thu, Mar 22, 2007 at 05:12:42AM +0100, Willy Tarreau wrote:
>  > On Wed, Mar 21, 2007 at 07:43:18PM -0400, Dave Jones wrote:
>  > > On Thu, Mar 22, 2007 at 12:24:33AM +0100, Willy Tarreau wrote:
>  > >  
>  > >  > Then a printk() on every open() should be enough. We've all been seeing
>  > >  > "Warning: tcpdump uses obsolete AF_PACKET"... and it finally disappeared.
>  > > 
>  > > There's a difference.  We have the source for tcpdump.
>  > 
>  > But what's the problem with "warning: process XXX uses obsolete raw driver
>  > and may not work anymore after 2007/XX/XX if not fixed" ?
> 
> The target audience isn't going to read it.

Yes they will if you write it with KERN_CRIT. It will show up on all their
consoles every time their process starts up. What is right is that those
people preferably use vendors' distro and generally do not compile their
kernels themselves, unless there are internal skills and good motivation
to do so.

Willy


  reply	other threads:[~2007-03-22  4:47 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-18 11:59 [PATCH] Delete obsolete RAW driver feature Robert P. J. Day
2007-03-18 15:57 ` Andi Kleen
2007-03-18 15:38   ` Robert P. J. Day
2007-03-20 16:57   ` Dave Jones
2007-03-20 18:14     ` Alan Cox
2007-03-20 18:47       ` Robert P. J. Day
2007-03-21 22:19       ` Andrew Morton
2007-03-21 23:19         ` Dave Jones
2007-03-21 23:27           ` Andrew Morton
2007-03-21 23:42             ` Dave Jones
2007-03-21 23:56               ` Andrew Morton
2007-03-22  0:10         ` Alan Cox
2007-03-21 23:13           ` Andrew Morton
2007-03-21 23:24             ` Willy Tarreau
2007-03-21 23:43               ` Dave Jones
2007-03-22  4:12                 ` Willy Tarreau
2007-03-22  4:17                   ` Dave Jones
2007-03-22  4:45                     ` Willy Tarreau [this message]
2007-03-22  5:02                       ` Dave Jones
2007-03-22  5:53                         ` Willy Tarreau
2007-03-22  6:10                           ` Dave Jones

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=20070322044540.GA32191@1wt.eu \
    --to=w@1wt.eu \
    --cc=akpm@linux-foundation.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=andi@firstfloor.org \
    --cc=bunk@stusta.de \
    --cc=davej@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rpjday@mindspring.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;
as well as URLs for NNTP newsgroup(s).