public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Julien Oster <usenet-20040502@usenet.frodoid.org>
To: Peter Osterlund <petero2@telia.com>
Cc: Julien Oster <lkml-7994@mc.frodoid.org>,
	Frediano Ziglio <freddyz77@tin.it>,
	axboe@suse.de, linux-kernel@vger.kernel.org,
	Andrew Morton <akpm@osdl.org>
Subject: Re: Packet writing problems
Date: Wed, 18 Aug 2004 10:25:54 +0200	[thread overview]
Message-ID: <87fz6k6eel.fsf@killer.ninja.frodoid.org> (raw)
In-Reply-To: <m3y8kdibgh.fsf@telia.com> (Peter Osterlund's message of "18 Aug 2004 01:36:30 +0200")

Peter Osterlund <petero2@telia.com> writes:

Hello Peter,

>> The following patch on top of your patch adds all commonly used media
>> types to the output and changes CD-R and CD-RW to be detected by
>> profile type. It also reports unconforming non-standard profiles as
>> well as profiles which have a MMC profile definition but are unknown
>> as of the current MMC3 revision.

> Will any of those printk's ever get printed? Media types that can't be
> handled by the packet driver aren't supposed to make it past the
> pkt_good_disc() test.

Quickly looking through it, pkt_good_disc() does the same and drops
media types with unsuitable or invalid profiles.

So my patch is really not useful at that place.

But couldn't you move the "inserted disc is..." messages to
pkt_good_disc()? In the current source you basically duplicate the
switch statement which checks the profile. The printks could be in the
pkt_good_disc() check just as well.

There all profiles might be included and the corresponding media type
printed out, so that the user knows why his disc is unsuitable
(i.e. it's a CD-ROM or DVD-ROM and doesn't do any writing at all).

Regards,
Julien

  reply	other threads:[~2004-08-18  8:30 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-16 15:16 Packet writing problems Frediano Ziglio
2004-08-16 18:50 ` Peter Osterlund
2004-08-16 19:09   ` Peter Osterlund
2004-08-16 19:51     ` Frediano Ziglio
2004-08-16 19:55     ` Frediano Ziglio
2004-08-17 19:59       ` Peter Osterlund
2004-08-17 20:24         ` Peter Osterlund
2004-08-17 23:31         ` Julien Oster
2004-08-17 23:36           ` Peter Osterlund
2004-08-18  8:25             ` Julien Oster [this message]
2004-08-18  8:38               ` Julien Oster
2004-08-18  8:48                 ` Julien Oster
     [not found] <20040818125719.GA6021@linux-ari.internal>
2004-08-18 17:08 ` Julien Oster
2004-08-19  6:56   ` Alex Riesen

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=87fz6k6eel.fsf@killer.ninja.frodoid.org \
    --to=usenet-20040502@usenet.frodoid.org \
    --cc=akpm@osdl.org \
    --cc=axboe@suse.de \
    --cc=freddyz77@tin.it \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkml-7994@mc.frodoid.org \
    --cc=petero2@telia.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