public inbox for linux-ide@vger.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Tom Yan <tom.ty89@gmail.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: Fri, 08 Jul 2016 17:49:58 -0700	[thread overview]
Message-ID: <1468025398.2390.24.camel@HansenPartnership.com> (raw)
In-Reply-To: <CAGnHSEkLer=GRZxoc=AmS7J_oe945hSdUV2TisSuvfXdCPQ2Ow@mail.gmail.com>

On Fri, 2016-07-08 at 19:38 +0000, Tom Yan wrote:
> On 8 July 2016 at 17:29, James Bottomley
> <James.Bottomley@hansenpartnership.com> wrote:
> > Or we could simply patch sg_sanitze to issue the ATA_16 pass 
> > through when it sees a sata device ...
> > 
> 
> Ugh that sounds ugly to me. Anyway that's off-topic.

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.

James


  reply	other threads:[~2016-07-09  0:50 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 [this message]
2016-07-11  6:35           ` Tom Yan
2016-10-26 22:44             ` Mark Lord

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=1468025398.2390.24.camel@HansenPartnership.com \
    --to=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