From: Mark Lord <liml@rtr.ca>
To: Tejun Heo <htejun@gmail.com>
Cc: Jeff Garzik <jeff@garzik.org>,
"linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>
Subject: Re: [PATCH 2.6.22-rc6] sata_inic162x: add big fat warning about broken LBA48 support
Date: Thu, 28 Jun 2007 13:50:05 -0400 [thread overview]
Message-ID: <4683F4CD.2090106@rtr.ca> (raw)
In-Reply-To: <4683DCD3.1040303@gmail.com>
Tejun Heo wrote:
> sata_inic162x can't do LBA48 properly yet. Whine loudly about it to
> reduce confusion.
Why not whine only when an affected device is actually present?
Cheers from OLS.
next prev parent reply other threads:[~2007-06-28 17:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-28 16:07 [PATCH 2.6.22-rc6] sata_inic162x: add big fat warning about broken LBA48 support Tejun Heo
2007-06-28 16:14 ` Greg Freemyer
2007-06-28 16:27 ` Tejun Heo
2007-06-28 16:35 ` Alan Cox
2007-06-28 16:59 ` Greg Freemyer
2007-06-28 17:50 ` Mark Lord [this message]
2007-06-28 17:51 ` Jeff Garzik
2007-06-28 17:53 ` Tejun Heo
2007-06-28 17:55 ` Jeff Garzik
2007-06-29 1:15 ` Mark Lord
2007-06-29 1:32 ` Tejun Heo
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=4683F4CD.2090106@rtr.ca \
--to=liml@rtr.ca \
--cc=htejun@gmail.com \
--cc=jeff@garzik.org \
--cc=linux-ide@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 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).