From: Jeff Garzik <jgarzik@pobox.com>
To: Tejun Heo <htejun@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: About mod15write workaround
Date: Fri, 13 May 2005 12:58:39 -0400 [thread overview]
Message-ID: <4284DCBF.6070208@pobox.com> (raw)
In-Reply-To: <20050513051057.GA12915@htj.dyndns.org>
Tejun Heo wrote:
> Hello Jeff.
>
> Can you tell me if/when mod15write workaround will be merged? It's
> been around for a while now and I haven't received any malfunciton
> report yet. Do you care to merging it into libata-dev-2.6?
That's in the queue, but queue processing is very slow ATM. Watch for
things appearing in the new git repositories.
Jeff
prev parent reply other threads:[~2005-05-13 16:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-13 5:10 About mod15write workaround Tejun Heo
2005-05-13 16:58 ` Jeff Garzik [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=4284DCBF.6070208@pobox.com \
--to=jgarzik@pobox.com \
--cc=htejun@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@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