linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alan <alan@lxorguk.ukuu.org.uk>
To: Mark Lord <liml@rtr.ca>
Cc: Jeff Garzik <jgarzik@pobox.com>, Tejun Heo <htejun@gmail.com>,
	IDE/ATA development list <linux-ide@vger.kernel.org>
Subject: Re: [PATCH] libata: check cdb len per dev instead of per host
Date: Thu, 1 Feb 2007 17:16:13 +0000	[thread overview]
Message-ID: <20070201171613.72091b81@localhost.localdomain> (raw)
In-Reply-To: <45C21C21.2060800@rtr.ca>

On Thu, 01 Feb 2007 11:58:09 -0500
Mark Lord <liml@rtr.ca> wrote:

> Fix libata to perform CDB len validation per device
> rather than per host.  This way, validation still works
> when we have a mix of 12-byte and 16-byte devices on
> a common host interface.#

Users can pass 16byte commands in the "safe" list of commands so can spam
the log via the printk

NAK


  reply	other threads:[~2007-02-01 17:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-01 16:58 [PATCH] libata: check cdb len per dev instead of per host Mark Lord
2007-02-01 17:16 ` Alan [this message]
2007-02-01 17:28   ` 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=20070201171613.72091b81@localhost.localdomain \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=htejun@gmail.com \
    --cc=jgarzik@pobox.com \
    --cc=liml@rtr.ca \
    --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).