From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
Cc: Jeff Garzik <jgarzik@pobox.com>, Jacob <fun2program8@yahoo.com>,
Christopher Hogan <chris.c.hogan@gmail.com>,
Robert Hancock <hancockrwd@gmail.com>,
linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] libata: add warning about possible HPA compatibility issue
Date: Tue, 26 May 2009 00:16:12 +0100 [thread overview]
Message-ID: <20090526001612.52cd484e@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <200905260115.00794.bzolnier@gmail.com>
> > Tejun has a patch in the queue which exposes the HPA and real sizes to
> > the OS
>
> In queue for 2.6.30?
2.6.30 merge window is closed, as you well kow
> I fully agree w.r.t to proper handling of HPA but we need "something" in
> the meantime because it is *real* issue resulting in *real* users filling
> *real* bug-reports (which unfortunately always get assigned to me first
> so I'm needlessly wasting my time on them).
The merge window is closed. This is a 2.6.31 discussion and randomly
adding bogus printks to the kernel won't help because
- Users have no idea what they mean
- Distros boot with "quiet" so users don't see them anyway
It would be good to get Tejun's patch upstream and also runtime HPA
switching.
> IOW Please stop downplaying bug #13365 which this patch tries to alleviate.
I'm still not convinced 13365 is an HPA problem entirely - but there are
certainly other HPA confusions here and there.
> I'm adding Andrew to cc:...
Hello Andrew ;)
Alan
prev parent reply other threads:[~2009-05-25 23:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-25 21:48 Bartlomiej Zolnierkiewicz
2009-05-25 22:20 ` Alan Cox
2009-05-25 22:36 ` Bartlomiej Zolnierkiewicz
2009-05-25 22:38 ` Alan Cox
2009-05-25 23:15 ` Bartlomiej Zolnierkiewicz
2009-05-25 23:16 ` Alan Cox [this message]
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=20090526001612.52cd484e@lxorguk.ukuu.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=akpm@linux-foundation.org \
--cc=bzolnier@gmail.com \
--cc=chris.c.hogan@gmail.com \
--cc=fun2program8@yahoo.com \
--cc=hancockrwd@gmail.com \
--cc=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®