From: Matthew Wilcox <matthew@wil.cx>
To: Jeff Garzik <jeff@garzik.org>
Cc: linux-ide@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] libata: Prepare for hard drives w/ non-512 sector sizes
Date: Wed, 8 Apr 2009 12:32:43 -0600 [thread overview]
Message-ID: <20090408183243.GK20983@parisc-linux.org> (raw)
In-Reply-To: <20090408065955.GA29845@havoc.gtf.org>
On Wed, Apr 08, 2009 at 02:59:55AM -0400, Jeff Garzik wrote:
> I checked this into libata-dev.git#sectsize and #NEXT... comments
> welcome. It's willy's patch, cut down such that it introduces no
> major behavior changes [READ CAPACITY improves slightly].
Umm. If you wanted me to split the patch up, why didn't you ask?
I really do think I should be credited as 'Author' here. You credit me
in the patch description, but the automated tools don't show that.
> @@ -2354,10 +2355,25 @@ saving_not_supp:
> */
> static unsigned int ata_scsiop_read_cap(struct ata_scsi_args *args, u8 *rbuf)
> {
> - u64 last_lba = args->dev->n_sectors - 1; /* LBA of the last block */
> + struct ata_device *dev = args->dev;
> + u64 last_lba = dev->n_sectors - 1; /* LBA of the last block */
> + u32 sector_size;
> + u8 log_per_phys = 1;
This was a bug I had fixed, but possibly not sent out. It should be 0,
not 1 (it's the power of 2, not the raw count).
--
Matthew Wilcox Intel Open Source Technology Centre
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours. We can't possibly take such
a retrograde step."
next prev parent reply other threads:[~2009-04-08 18:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-08 6:59 [PATCH] libata: Prepare for hard drives w/ non-512 sector sizes Jeff Garzik
2009-04-08 18:32 ` Matthew Wilcox [this message]
2009-04-08 18:47 ` Jeff Garzik
2009-04-08 18:56 ` Matthew Wilcox
2009-04-08 19:08 ` Jeff Garzik
2009-04-08 19:13 ` Matthew Wilcox
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=20090408183243.GK20983@parisc-linux.org \
--to=matthew@wil.cx \
--cc=jeff@garzik.org \
--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 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.