From: Jeff Garzik <jgarzik@pobox.com>
To: albertl@mail.com
Cc: Linux IDE <linux-ide@vger.kernel.org>
Subject: Re: [PATCH] libata-dev: recognize WRITE_MULTI_FUA_EXT for r/w multiple
Date: Fri, 03 Mar 2006 12:22:35 -0500 [thread overview]
Message-ID: <44087B5B.9030909@pobox.com> (raw)
In-Reply-To: <4407AB1D.2080506@tw.ibm.com>
Albert Lee wrote:
> Jeff,
>
> Changes:
> Recognize ATA_CMD_WRITE_MULTI_FUA_EXT as r/w multiple commands.
>
> Patch against the irq-pio branch
> (1ed82ae3df3882bfcb5bfe5e9f97e4e8e23af299).
>
> For your review, thanks.
>
> Albert
>
> Signed-off-by: Albert Lee <albertcc@tw.ibm.com>
I would request that you adjust your patch submission slightly. Stuff
like "Jeff," "Changes:", "Patch against...", "For your review", "Albert"
all must be hand-edited out before applying the patch. Everything
before the "---" terminator is copied directly into the kernel changelog.
Take a look at Tejun's recent patches for an example. The message body
of his emailed submissions look like:
[change description]
[signed-off-by]
---
[notes, comments, insults, etc. :)]
> --- irq-pio/include/linux/ata.h 2006-03-02 15:22:58.000000000 +0800
> +++ irq-pio-catchup/include/linux/ata.h 2006-03-02 17:05:17.000000000 +0800
> @@ -314,7 +314,8 @@ static inline int is_multi_taskfile(stru
> return (tf->command == ATA_CMD_READ_MULTI) ||
> (tf->command == ATA_CMD_WRITE_MULTI) ||
> (tf->command == ATA_CMD_READ_MULTI_EXT) ||
> - (tf->command == ATA_CMD_WRITE_MULTI_EXT);
> + (tf->command == ATA_CMD_WRITE_MULTI_EXT) ||
> + (tf->command == ATA_CMD_WRITE_MULTI_FUA_EXT);
Applied to irq-pio branch, though Mark Lord makes a correct point. We
may have to create a whitelist for PATA devices that support FUA, rather
than a blacklist. Something to think about...
Thanks,
Jeff
prev parent reply other threads:[~2006-03-03 17:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-03 2:34 [PATCH] libata-dev: recognize WRITE_MULTI_FUA_EXT for r/w multiple Albert Lee
2006-03-03 14:26 ` Mark Lord
2006-03-03 14:28 ` Jens Axboe
2006-03-03 17:22 ` 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=44087B5B.9030909@pobox.com \
--to=jgarzik@pobox.com \
--cc=albertl@mail.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 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).