From: Hannes Reinecke <hare@suse.de>
To: Shaun Tancheff <shaun@tancheff.com>,
linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Tejun Heo <tj@kernel.org>, Christoph Hellwig <hch@lst.de>,
Tom Yan <tom.ty89@gmail.com>,
"Martin K . Petersen" <martin.petersen@oracle.com>,
Damien Le Moal <damien.lemoal@hgst.com>,
Josh Bingaman <josh.bingaman@seagate.com>,
Hannes Reinecke <hare@suse.com>,
Shaun Tancheff <shaun.tancheff@seagate.com>
Subject: Re: [PATCH v6 1/4] libata: Safely overwrite attached page in WRITE SAME xlat
Date: Mon, 22 Aug 2016 08:27:50 +0200 [thread overview]
Message-ID: <6d0c8773-dbf8-ea21-f3ca-dc1d05f52890@suse.de> (raw)
In-Reply-To: <20160822042321.24367-2-shaun@tancheff.com>
On 08/22/2016 06:23 AM, Shaun Tancheff wrote:
> Safely overwriting the attached page to ATA format from the SCSI formatted
> variant.
>
> Signed-off-by: Shaun Tancheff <shaun.tancheff@seagate.com>
> ---
> v6:
> - Fix bisect bug reported by Tom Yan <tom.ty89@gmail.com>
> - Change to use sg_copy_from_buffer as per Christoph Hellwig <hch@lst.de>
> v5:
> - Added prep patch to work with non-page aligned scatterlist pages
> and use kmap_atomic() to lock page during modification.
>
> drivers/ata/libata-scsi.c | 56 ++++++++++++++++++++++++++++++++++++++++++-----
> include/linux/ata.h | 26 ----------------------
> 2 files changed, 51 insertions(+), 31 deletions(-)
>
Reviewed-by: Hannes Reinecke <hare@suse.com>
Cheers,
Hannes
--
Dr. Hannes Reinecke Teamlead Storage & Networking
hare@suse.de +49 911 74053 688
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: F. Imendörffer, J. Smithard, J. Guild, D. Upmanyu, G. Norton
HRB 21284 (AG Nürnberg)
next prev parent reply other threads:[~2016-08-22 6:27 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-22 4:23 [PATCH v6 0/4] SCT Write Same Shaun Tancheff
2016-08-22 4:23 ` [PATCH v6 1/4] libata: Safely overwrite attached page in WRITE SAME xlat Shaun Tancheff
2016-08-22 6:27 ` Hannes Reinecke [this message]
2016-08-22 19:27 ` Tom Yan
2016-08-22 19:51 ` Shaun Tancheff
2016-08-22 20:12 ` Tom Yan
2016-08-22 21:20 ` Tom Yan
2016-08-22 22:00 ` Shaun Tancheff
2016-08-22 23:49 ` Tom Yan
2016-08-23 1:01 ` Shaun Tancheff
2016-08-23 5:26 ` Tom Yan
2016-08-23 6:20 ` Shaun Tancheff
2016-08-23 7:53 ` Tom Yan
2016-08-23 8:42 ` Shaun Tancheff
2016-08-23 9:04 ` Tom Yan
2016-08-24 3:33 ` Martin K. Petersen
2016-08-24 5:31 ` Tom Yan
2016-08-24 21:28 ` Shaun Tancheff
2016-08-25 6:31 ` Tom Yan
2016-08-25 7:18 ` Shaun Tancheff
2016-08-22 4:23 ` [PATCH v6 2/4] Add support for SCT Write Same Shaun Tancheff
2016-08-22 6:27 ` Hannes Reinecke
2016-08-22 19:20 ` Tom Yan
2016-08-22 19:43 ` Shaun Tancheff
2016-08-22 20:14 ` Tom Yan
2016-08-22 22:07 ` Shaun Tancheff
2016-08-22 23:09 ` Tom Yan
2016-08-23 0:36 ` Shaun Tancheff
2016-08-23 5:55 ` Tom Yan
2016-08-23 6:11 ` Shaun Tancheff
2016-08-23 7:57 ` Tom Yan
2016-08-23 10:37 ` Tom Yan
2016-08-23 10:56 ` Shaun Tancheff
2016-08-24 5:57 ` Tom Yan
2016-08-24 6:10 ` Tom Yan
2016-08-24 22:04 ` Shaun Tancheff
2016-08-25 6:23 ` Tom Yan
2016-08-25 7:31 ` Shaun Tancheff
2016-08-22 4:23 ` [PATCH v6 3/4] SCT Write Same / DSM Trim Shaun Tancheff
2016-08-22 6:30 ` Hannes Reinecke
2016-08-24 18:08 ` [PATCH v6 3/4 RESEND] " Shaun Tancheff
2016-08-25 7:01 ` Tom Yan
2016-08-25 8:03 ` Shaun Tancheff
2016-08-25 9:30 ` Tom Yan
2016-08-22 8:31 ` [PATCH v6 3/4] " Tom Yan
2016-08-22 8:33 ` Tom Yan
2016-08-22 15:04 ` Shaun Tancheff
2016-08-22 17:02 ` Tom Yan
2016-08-22 18:00 ` Shaun Tancheff
2016-08-22 18:52 ` Tom Yan
2016-08-22 20:57 ` Tom Yan
2016-08-22 4:23 ` [PATCH v6 4/4] SCT Write Same handle ATA_DFLAG_PIO Shaun Tancheff
2016-08-22 6:31 ` Hannes Reinecke
2016-08-22 6:32 ` [PATCH v6 0/4] SCT Write Same Hannes Reinecke
2016-08-25 15:28 ` Tejun Heo
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=6d0c8773-dbf8-ea21-f3ca-dc1d05f52890@suse.de \
--to=hare@suse.de \
--cc=damien.lemoal@hgst.com \
--cc=hare@suse.com \
--cc=hch@lst.de \
--cc=josh.bingaman@seagate.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=shaun.tancheff@seagate.com \
--cc=shaun@tancheff.com \
--cc=tj@kernel.org \
--cc=tom.ty89@gmail.com \
/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