All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Al Viro <viro@ftp.linux.org.uk>,
	Christoph Hellwig <hch@infradead.org>,
	Adrian Bunk <bunk@kernel.org>,
	perex@suse.cz, linux-kernel@vger.kernel.org
Subject: Re: [-mm patch] unexport sys_{open,read}
Date: Mon, 10 Sep 2007 10:54:10 -0700	[thread overview]
Message-ID: <20070910105410.25e1d54c.akpm@linux-foundation.org> (raw)
In-Reply-To: <20070910184454.6c2a8ab9@the-village.bc.nu>

On Mon, 10 Sep 2007 18:44:54 +0100 Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:

> > A single kernel release seems sufficient.  It gives the maintainers of such
> > code time to hear about the breakage and time to fix it.
> 
> Users don't report warnings generally. They won't even see modprobe
> warnings or anything in dmesg. Short of using their sound card to scream
> "Next release you are screwed" they won't notice (and if you the sound
> card trick they'll think they got rooted....)
> 

I once made the mistake of putting a "please tell andrewm@uow.edu.au" printk
in 3c59x.c.  My inbox nearly died.  Then there's that damned "PCI bus hidden
behind transparent bus" printk which I've actually removed from -mm because
so many people keep reporting it and we don't do anything about it.

All it takes is a couple of people to report the problem to the maintainer
over a few-weeks period.  It doesn't seem unreasonable to expect this to
happen.

  reply	other threads:[~2007-09-10 17:55 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-09 20:25 [-mm patch] unexport sys_{open,read} Adrian Bunk
2007-09-09 20:39 ` Christoph Hellwig
2007-09-09 21:59   ` Andrew Morton
2007-09-09 22:22     ` Adrian Bunk
2007-09-09 22:41       ` Arjan van de Ven
2007-09-09 23:18         ` Adrian Bunk
2007-09-10  9:08     ` Christoph Hellwig
2007-09-10  9:23       ` Andrew Morton
2007-09-10 12:03         ` Adrian Bunk
2007-09-10 12:31         ` Alan Cox
2007-09-10 12:43         ` Al Viro
2007-09-10 17:25           ` Andrew Morton
2007-09-10 17:44             ` Alan Cox
2007-09-10 17:54               ` Andrew Morton [this message]
2007-09-13 23:23                 ` Greg KH
2007-09-10 19:58             ` Adrian Bunk
2007-09-10 20:17               ` Andrew Morton
2007-09-10 22:18                 ` Adrian Bunk
2007-09-10 22:15                   ` Rene Herman
2007-09-10 22:41                     ` Adrian Bunk
2007-09-10 22:56                       ` Rene Herman
2007-09-10 15:14         ` Arjan van de Ven
2007-09-25 21:17           ` Dave Jones
2007-09-10 12:18   ` David Miller
2007-09-10 12:21     ` Christoph Hellwig
2007-09-18 14:10     ` Adrian Bunk
  -- strict thread matches above, loose matches on Subject: below --
2007-08-22  9:06 2.6.23-rc3-mm1 Andrew Morton
2007-08-27 21:27 ` [-mm patch] unexport sys_{open,read} Adrian Bunk
2007-08-27 22:53   ` Arjan van de Ven
2007-08-27 23:17     ` Adrian Bunk

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=20070910105410.25e1d54c.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=bunk@kernel.org \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=perex@suse.cz \
    --cc=viro@ftp.linux.org.uk \
    /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.