From: Jeff Garzik <jgarzik@pobox.com>
To: Christoph Hellwig <hch@lst.de>
Cc: linux-ide@vger.kernel.org, stable@kernel.org
Subject: Re: [PATCH v2] libata: fix ata_id_logical_per_physical_sectors
Date: Wed, 03 Feb 2010 12:42:13 -0500 [thread overview]
Message-ID: <4B69B575.9060201@pobox.com> (raw)
In-Reply-To: <20100203173721.GA21703@lst.de>
On 02/03/2010 12:37 PM, Christoph Hellwig wrote:
> Jeff, ping? Without this patch the minimum I/O size for 4k drives will
> be reported incorrectly, which will make paritions misaligned on modern
> distros.
It's queued locally. I'm waiting to push on the flush_dache_page()
discussion for 2.6.33, but I'll make sure your patch gets pushed today
one way or the other.
Jeff
next prev parent reply other threads:[~2010-02-03 17:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-28 10:42 [PATCH] libata: fix ata_id_logical_per_physical_sectors Christoph Hellwig
2010-01-28 10:56 ` Sergei Shtylyov
2010-01-28 10:59 ` Christoph Hellwig
2010-01-28 12:30 ` [PATCH v2] " Christoph Hellwig
2010-02-03 17:37 ` Christoph Hellwig
2010-02-03 17:42 ` Jeff Garzik [this message]
2010-02-03 18:14 ` Martin K. Petersen
2010-02-03 18:17 ` Christoph Hellwig
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=4B69B575.9060201@pobox.com \
--to=jgarzik@pobox.com \
--cc=hch@lst.de \
--cc=linux-ide@vger.kernel.org \
--cc=stable@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).