All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <htejun@gmail.com>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: albertcc@tw.ibm.com, linux-ide@vger.kernel.org
Subject: Re: [PATCH 3/4] libata: add per-device max_sectors
Date: Mon, 13 Feb 2006 09:47:57 +0900	[thread overview]
Message-ID: <43EFD73D.4070207@gmail.com> (raw)
In-Reply-To: <43EF8E61.5040409@pobox.com>

Jeff Garzik wrote:
> 
> applied 3-4, though note that the Axboe code mentioned in the comment is 
> now in the kernel, so lba48 can be fixed properly.
> 

Care to tell me which commit it was?  I don't really understand the comment.

Thanks.

-- 
tejun

  reply	other threads:[~2006-02-13  0:48 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-12 14:32 [PATCHSET] libata: make some configurations per-dev Tejun Heo
2006-02-12 14:32 ` [PATCH 2/4] libata: move cdb_len for host to device Tejun Heo
2006-02-12 14:32 ` [PATCH 1/4] libata: make ata_dev_knobble() per-device Tejun Heo
2006-02-12 19:29   ` Jeff Garzik
2006-02-12 14:32 ` [PATCH 4/4] libata: kill sht->max_sectors Tejun Heo
2006-02-12 14:32 ` [PATCH 3/4] libata: add per-device max_sectors Tejun Heo
2006-02-12 19:37   ` Jeff Garzik
2006-02-13  0:47     ` Tejun Heo [this message]
2006-02-13  4:58       ` Jeff Garzik
2006-02-15  7:24         ` [PATCH] libata: increase LBA48 max sectors to 65535 Tejun Heo
2006-02-15 13:07           ` Jens Axboe
2006-02-15 15:04             ` Tejun Heo
2006-02-15 15:12               ` Jens Axboe
2006-02-15 15:30                 ` Tejun Heo
2006-02-15 19:03                 ` Mark Lord
2006-02-15 20:21                 ` Jeff Garzik
2006-02-15 23:05                   ` Mark Lord
2006-02-20 11:23                     ` Jeff Garzik
2006-02-20 13:54                       ` Mark Lord
2006-02-20 13:58                         ` Jens Axboe
2006-02-16  7:42                   ` Jens Axboe
2006-02-20 11:25                     ` Jeff Garzik
2006-02-20 11:44                       ` Jens Axboe
2006-02-20 21:59           ` Jeff Garzik

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=43EFD73D.4070207@gmail.com \
    --to=htejun@gmail.com \
    --cc=albertcc@tw.ibm.com \
    --cc=jgarzik@pobox.com \
    --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 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.