From: Christoph Hellwig <hch@lst.de>
To: jgarzik@pobox.com
Cc: linux-ide@vger.kernel.org
Subject: libata: use the WRITE_SAME_16 define
Date: Thu, 10 Dec 2009 10:36:01 +0100 [thread overview]
Message-ID: <20091210093601.GA30917@lst.de> (raw)
Now that the scsi tree has hit mainline we can use the newly added WRITE_SAME_16
define.
Signed-off-by: Christoph Hellwig <hch@lst.de>
Index: linux-2.6/drivers/ata/libata-scsi.c
===================================================================
--- linux-2.6.orig/drivers/ata/libata-scsi.c 2009-12-10 10:21:05.735254334 +0100
+++ linux-2.6/drivers/ata/libata-scsi.c 2009-12-10 10:21:29.562255983 +0100
@@ -3022,7 +3022,7 @@ static inline ata_xlat_func_t ata_get_xl
case WRITE_16:
return ata_scsi_rw_xlat;
- case 0x93 /*WRITE_SAME_16*/:
+ case WRITE_SAME_16:
return ata_scsi_write_same_xlat;
case SYNCHRONIZE_CACHE:
next reply other threads:[~2009-12-10 9:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-10 9:36 Christoph Hellwig [this message]
2009-12-17 6:03 ` libata: use the WRITE_SAME_16 define 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=20091210093601.GA30917@lst.de \
--to=hch@lst.de \
--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 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).