From: Jeff Garzik <jeff@garzik.org>
To: Mark Lord <liml@rtr.ca>
Cc: IDE/ATA development list <linux-ide@vger.kernel.org>,
Tejun Heo <htejun@gmail.com>
Subject: Re: [PATCH] RESEND: libata: check cdb len per dev instead of per host
Date: Fri, 02 Mar 2007 19:26:33 -0500 [thread overview]
Message-ID: <45E8C0B9.4050402@garzik.org> (raw)
In-Reply-To: <45C37699.7000306@rtr.ca>
Mark Lord wrote:
> Resending, with s/printk/DPRINTK/ as pointed out by Alan.
>
> 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.
>
> Signed-off-by: Mark Lord <mlord@pobox.com>
applied, though I am disappointed that we had to add this check (as well
as another one in an unrelated Tejun patch) to the fast path
prev parent reply other threads:[~2007-03-03 0:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-02 17:36 [PATCH] RESEND: libata: check cdb len per dev instead of per host Mark Lord
2007-03-03 0:26 ` Jeff Garzik [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=45E8C0B9.4050402@garzik.org \
--to=jeff@garzik.org \
--cc=htejun@gmail.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).