From: Jeff Garzik <jeff@garzik.org>
To: Alan Cox <alan@linux.intel.com>
Cc: jeff@garzik.org.com, linux-kernel@vger.kernel.org,
linux-ide@vger.kernel.org
Subject: Re: [PATCH 2/5] Subject: [PATCH] pata_efar: add locking for parallel scanning
Date: Mon, 01 Mar 2010 15:12:14 -0500 [thread overview]
Message-ID: <4B8C1F9E.8040703@garzik.org> (raw)
In-Reply-To: <20100217131556.16884.47082.stgit@localhost.localdomain>
On 02/17/2010 08:16 AM, Alan Cox wrote:
> From: Bartlomiej Zolnierkiewicz<bzolnier@gmail.com>
>
> Add clearing of UDMA enable bit also for PIO modes and then add
> an extra locking for parallel scanning.
>
> This is similar change as commit 60c3be3 for ata_piix host driver
> and while pata_efar doesn't enable parallel scan yet the race could
> probably also be triggered by requesting re-scanning of both ports
> at the same time using SCSI sysfs interface.
>
> [Ported to current kernel without other patch dependancies by
> Alan Cox]
>
> Original is
> Signed-off-by: Bartlomiej Zolnierkiewicz<bzolnier@gmail.com>
>
> This one is
> Signed-off-by: Alan Cox<alan@linux.intel.com>
> ---
>
> drivers/ata/pata_efar.c | 15 +++++++++++++++
> 1 files changed, 15 insertions(+), 0 deletions(-)
applied 2-5
next prev parent reply other threads:[~2010-03-01 20:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-17 13:15 [PATCH 1/5] libata: Pass host flags into the pci helper Alan Cox
2010-02-17 13:16 ` [PATCH 2/5] Subject: [PATCH] pata_efar: add locking for parallel scanning Alan Cox
2010-03-01 20:12 ` Jeff Garzik [this message]
2010-02-17 13:17 ` [PATCH 3/5] Subject: [PATCH] pata_atiixp: " Alan Cox
2010-02-17 13:17 ` [PATCH 4/5] pata_atiixp: enable parallel scan Alan Cox
2010-02-17 13:17 ` [PATCH 5/5] pata_efar: Enable PARALLEL_SCAN Alan Cox
2010-02-23 7:27 ` [PATCH 1/5] libata: Pass host flags into the pci helper Jeff Garzik
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=4B8C1F9E.8040703@garzik.org \
--to=jeff@garzik.org \
--cc=alan@linux.intel.com \
--cc=jeff@garzik.org.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.