public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@suse.de>
To: Mike Christie <michaelc@cs.wisc.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] update max_sectors documentation
Date: Wed, 8 Mar 2006 11:17:00 +0100	[thread overview]
Message-ID: <20060308101659.GJ4595@suse.de> (raw)
In-Reply-To: <1141777621.5594.3.camel@max>

On Tue, Mar 07 2006, Mike Christie wrote:
> Hi Jens,
> 
> I was looking over Kai's scsi command size email and was going to try
> and add it to some block docs and noticed I did not send the update to
> the max_sectors biodoc.txt. Sorry about that. Here is the patch against
> 2.6.16-rc5.
> 
> The max_sectors has been split into max_hw_sectors and max_sectors for some
> time. A patch to have blk_queue_max_sectors enforce this was sent by
> me and it broke IDE. This patch updates the documentation.

Thanks Mike, committed.

-- 
Jens Axboe


      reply	other threads:[~2006-03-08 10:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-08  0:27 [PATCH] update max_sectors documentation Mike Christie
2006-03-08 10:17 ` Jens Axboe [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=20060308101659.GJ4595@suse.de \
    --to=axboe@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michaelc@cs.wisc.edu \
    /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