linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Tejun Heo <htejun@gmail.com>
Cc: linux-ide@vger.kernel.org
Subject: Re: [PATCH] libata: fix handling of port actions in per-dev action mask
Date: Fri, 19 Jan 2007 19:22:56 -0500	[thread overview]
Message-ID: <45B160E0.3030905@pobox.com> (raw)
In-Reply-To: <20070118082218.GR10987@htj.dyndns.org>

Tejun Heo wrote:
> libata EH ignores port-wide actions in per-dev action mask.  However,
> device resume requests EH_SOFTRESET using per-dev action mask.  Under
> certain circumstances, this results in not resetting frozen port after
> resuming which causes failure of all commands.
> 
> This patch allows port-wide actions to be requested in per-dev action
> mask.  Before EH recovery starts, port-wide actions will be collected.
> 
> Signed-off-by: Tejun Heo <htejun@gmail.com>
> ---
> After being tested, this one should go into -stable too.

applied to #upstream-fixes



      reply	other threads:[~2007-01-20  0:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-18  8:22 [PATCH] libata: fix handling of port actions in per-dev action mask Tejun Heo
2007-01-20  0:22 ` 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=45B160E0.3030905@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=htejun@gmail.com \
    --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).