public inbox for linux-ide@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark Lord <kernel@start.ca>
To: Tom Yan <tom.ty89@gmail.com>,
	James Bottomley <James.Bottomley@hansenpartnership.com>
Cc: Tejun Heo <tj@kernel.org>,
	martin.petersen@oracle.com, dgilbert@interlog.com,
	linux-ide@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: [RFC] libata-scsi: introducing SANITIZE translation
Date: Wed, 26 Oct 2016 18:44:47 -0400	[thread overview]
Message-ID: <a38e505d-bb78-ac7c-d289-0460eef9449a@start.ca> (raw)
In-Reply-To: <CAGnHSEms1rwy7-+URRMrdggpk=_7YVijHwf1h93iBKW7zLxh8g@mail.gmail.com>

On 16-07-11 02:35 AM, Tom Yan wrote:
> I don't suppose there would be any problem doing it in userspace /
> with ATA PASS-THROUGH anyway.
..
>>> On 8 July 2016 at 17:29, James Bottomley
>>> <James.Bottomley@hansenpartnership.com> wrote:
..
>> Not really.  The point is that you've proposed something as an addition
>> to the kernel that can also be done in userspace.  Checking if it can
>> work easily there is like a barrier to entry.  If it works, then fine,
>> we're done.  If it throws up problems then we reconsider the kernel
>> route.

hdparm has full support for the SANITIZE commands in userspace.

-ml

      reply	other threads:[~2016-10-26 22:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-07 16:32 [RFC] libata-scsi: introducing SANITIZE translation tom.ty89
2016-07-07 16:47 ` James Bottomley
2016-07-08 16:20   ` Tom Yan
2016-07-08 17:29     ` James Bottomley
2016-07-08 19:38       ` Tom Yan
2016-07-09  0:49         ` James Bottomley
2016-07-11  6:35           ` Tom Yan
2016-10-26 22:44             ` Mark Lord [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=a38e505d-bb78-ac7c-d289-0460eef9449a@start.ca \
    --to=kernel@start.ca \
    --cc=James.Bottomley@hansenpartnership.com \
    --cc=dgilbert@interlog.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.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