From: Tejun Heo <htejun@gmail.com>
To: Jeff Garzik <jeff@garzik.org>
Cc: "linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [SATA] max-sect and sii-m15w branches merged
Date: Thu, 10 Aug 2006 20:25:56 +0900 [thread overview]
Message-ID: <44DB17C4.2070908@gmail.com> (raw)
In-Reply-To: <44DB106C.6090504@garzik.org>
Jeff Garzik wrote:
> I just merged the max-sect and sii-m15w branches into the upstream branch.
>
> This means that the following two changes are queued for 2.6.19:
>
> * increase max sectors from 200 to 256 (for lba28)
> * better mod15write support for sata_sil
Are we ready for m15w-iterate-over-large-write patch? It has been used
by many people for quite some time and works great. If you think we can
merge that patch, I'll port it over #upstream.
Thanks.
--
tejun
next prev parent reply other threads:[~2006-08-10 11:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-10 10:54 [SATA] max-sect and sii-m15w branches merged Jeff Garzik
2006-08-10 11:25 ` Tejun Heo [this message]
2006-08-10 12:00 ` Jeff Garzik
2006-08-10 12:41 ` Alan Cox
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=44DB17C4.2070908@gmail.com \
--to=htejun@gmail.com \
--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 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).