All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Wilcox <matthew@wil.cx>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Mark Lord <lkml@rtr.ca>, Matthias Andree <matthias.andree@gmx.de>,
	Douglas Gilbert <dougg@torque.net>, Mark Rustad <mrustad@mac.com>,
	linux-scsi@vger.kernel.org,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: sg regression in 2.6.16-rc5
Date: Wed, 1 Mar 2006 11:50:51 -0700	[thread overview]
Message-ID: <20060301185051.GC1598@parisc-linux.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0603011036110.22647@g5.osdl.org>

On Wed, Mar 01, 2006 at 10:42:12AM -0800, Linus Torvalds wrote:
> I wouldn't expect it to. Most people use ATA for that, and it tends to 
> have lower limits than most SCSI HBA's (well, at least the old PATA), so 
> the change - if any - should at most change some of the sg.c limits to be 
> no less than what SG_IO has had on ATA forever.
> 
> Not that I expect people to have a SCSI CD/DVD drive anyway in this day 
> and age, so the sg.c changes probably won't show up at all.

My wife's last two laptops have both had 'SCSI' CD/DVD -- firewire on
the Vaio and SATA on the Lifebook.  Neither time have distros been
prepared to deal with such things ;-(

http://www.leog.net/fujp_forum/topic.asp?TOPIC_ID=9038 shows it's not
just my distro of choice that has problems with SATA ATAPI.
Unfortunately, the one-line change to enable that by default was too
late for 2.6.16, according to jgarzik.  I just hope all the distros
patch it.

  reply	other threads:[~2006-03-01 18:50 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-28 17:54 sg regression in 2.6.16-rc5 Mark Rustad
2006-02-28 19:53 ` Douglas Gilbert
2006-02-28 20:38   ` Kai Makisara
2006-03-01  2:04     ` Douglas Gilbert
2006-03-01  2:08     ` Mark Rustad
2006-03-01  8:38   ` Matthias Andree
2006-03-01 18:28     ` Linus Torvalds
2006-03-01 18:32       ` Mark Lord
2006-03-01 18:42         ` Linus Torvalds
2006-03-01 18:50           ` Matthew Wilcox [this message]
2006-03-03 18:27           ` Steve Byan
2006-03-03 18:55             ` Linus Torvalds
2006-03-03 19:13               ` Steve Byan
2006-03-03 19:42               ` Jeff Garzik
2006-03-03 20:09                 ` Linus Torvalds
2006-03-03 20:30                   ` Jeff Garzik
2006-03-01 19:33       ` Douglas Gilbert
2006-03-01 20:42         ` Mike Christie
2006-03-01 22:30           ` James Bottomley
2006-03-01 22:56             ` Mike Christie
2006-03-01 21:06         ` Kai Makisara
2006-03-02 19:50           ` Douglas Gilbert
2006-03-02 21:25             ` Linus Torvalds
2006-03-02 23:08               ` Matthias Andree
2006-03-02 23:20                 ` Linus Torvalds
2006-03-03  0:02                   ` Linus Torvalds
2006-03-03  0:12                     ` Linus Torvalds
2006-03-03 16:43                   ` Douglas Gilbert
2006-03-03 17:17                     ` Linus Torvalds
2006-03-02 23:06             ` Matthias Andree
  -- strict thread matches above, loose matches on Subject: below --
2006-03-02 23:04 Falkinder, David Malcolm
2006-03-02 23:04 ` Falkinder, David Malcolm
2006-03-03 20:24 Falkinder, David Malcolm
2006-03-03 21:54 ` Linus Torvalds

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=20060301185051.GC1598@parisc-linux.org \
    --to=matthew@wil.cx \
    --cc=dougg@torque.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=lkml@rtr.ca \
    --cc=matthias.andree@gmx.de \
    --cc=mrustad@mac.com \
    --cc=torvalds@osdl.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.