From: Jeff Garzik <jgarzik@pobox.com>
To: Prabhakar Kushwaha <prabhakar@freescale.com>
Cc: linux-ide@vger.kernel.org, Ashish Kalra <B00888@freescale.com>,
linuxppc-dev@lists.ozlabs.org, meet2prabhu@gmail.com
Subject: Re: [PATCH][v3] driver/FSL SATA:Fix wrong Device Error Register usage
Date: Mon, 14 Mar 2011 03:05:07 -0400 [thread overview]
Message-ID: <4D7DBE23.10109@pobox.com> (raw)
In-Reply-To: <1299655038-727-1-git-send-email-prabhakar@freescale.com>
On 03/09/2011 02:17 AM, Prabhakar Kushwaha wrote:
> When a single device error is detected, the device under the error is indicated
> by the error bit set in the DER. There is a one to one mapping between register
> bit and devices on Port multiplier(PMP) i.e. bit 0 represents PMP device 0 and
> bit 1 represents PMP device 1 etc.
>
> Current implementation treats Device error register value as device number not
> set of bits representing multiple device on PMP. It is changed to consider bit
> level.
> No need to check for each set bit as all command is going to be aborted.
>
> Signed-off-by: Ashish Kalra<B00888@freescale.com>
> Signed-off-by: Prabhakar Kushwaha<prabhakar@freescale.com>
> ---
>
> git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git (branch master)
>
> This patch is already gone through review of linuxppc-dev mail list.
> Making CC linuxppc-dev@lists.ozlabs.org
>
> Changes for v2: Incorporated Sergei Shtylyov's comment
> - Put space after -
> - added a line
> Changes for v3: Incorporated David Laight's comment
> - Condition check for dereg 0 for hardware error
>
> drivers/ata/sata_fsl.c | 7 +++++--
> 1 files changed, 5 insertions(+), 2 deletions(-)
applied
prev parent reply other threads:[~2011-03-14 7:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-09 7:17 [PATCH][v3] driver/FSL SATA:Fix wrong Device Error Register usage Prabhakar Kushwaha
2011-03-14 4:12 ` Kushwaha Prabhakar-B32579
2011-03-14 7:05 ` 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=4D7DBE23.10109@pobox.com \
--to=jgarzik@pobox.com \
--cc=B00888@freescale.com \
--cc=linux-ide@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=meet2prabhu@gmail.com \
--cc=prabhakar@freescale.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;
as well as URLs for NNTP newsgroup(s).