From: Andrew Morton <akpm@linux-foundation.org>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Jeff Garzik <jeff@garzik.org>,
Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>,
linux-scsi@vger.kernel.org, Jens Axboe <jens.axboe@oracle.com>
Subject: Re: dmesg spam
Date: Mon, 4 Feb 2008 19:59:23 -0800 [thread overview]
Message-ID: <20080204195923.5d893a18.akpm@linux-foundation.org> (raw)
In-Reply-To: <1202157858.3096.114.camel@localhost.localdomain>
On Mon, 04 Feb 2008 14:44:18 -0600 James Bottomley <James.Bottomley@HansenPartnership.com> wrote:
>
> On Mon, 2008-02-04 at 15:24 -0500, Jeff Garzik wrote:
> > James Bottomley wrote:
> > > It's here in sr_ioctl.c:
> >
> > Ah, indeed. My grep-fu sucks today.
> >
> >
> > > I'm not averse to simply nuking the printk ... it's probably valueless
> > > in a modern kernel, since something dbussy is supposed to tell you to
> > > put a CD in the drive, not something in the kernel.
> >
> > The reverse... dbussy/HAL is implementing autodetection of media
> > insertion, by polling ad infinitum.
>
> Understood ... I meant the day of the user relying on a message from a
> kernel printk to tell them they need a CD in the drive is long over.
>
OK, sorry, I'm hopelessly full of it. These messages also are produced by
2.6.24, 2.6.23 and 2.6.23.1-49.fc8.
I don't think anyone would miss this message were it to bite the D key.
next prev parent reply other threads:[~2008-02-05 3:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-03 22:30 dmesg spam Andrew Morton
2008-02-04 14:24 ` Bartlomiej Zolnierkiewicz
2008-02-04 20:05 ` Andrew Morton
2008-02-04 20:14 ` Jeff Garzik
2008-02-04 20:20 ` James Bottomley
2008-02-04 20:24 ` Jeff Garzik
2008-02-04 20:44 ` James Bottomley
2008-02-05 3:59 ` Andrew Morton [this message]
2008-02-04 20:15 ` James Bottomley
2008-02-04 20:21 ` Jeff Garzik
2008-02-04 21:07 ` Andrew Morton
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=20080204195923.5d893a18.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=bzolnier@gmail.com \
--cc=jeff@garzik.org \
--cc=jens.axboe@oracle.com \
--cc=linux-scsi@vger.kernel.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.