linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tejun Heo <htejun@gmail.com>
To: "zhao, forrest" <forrest.zhao@intel.com>
Cc: Jeff Garzik <jgarzik@pobox.com>, linux-ide@vger.kernel.org
Subject: Re: [PATCH] libata: implement per-dev EH action mask	eh_info->dev_action[]
Date: Tue, 20 Jun 2006 17:08:32 +0900	[thread overview]
Message-ID: <4497AD00.6000703@gmail.com> (raw)
In-Reply-To: <1150786964.7132.117.camel@forrest26.sh.intel.com>

zhao, forrest wrote:
> On Mon, 2006-06-19 at 18:27 +0900, Tejun Heo wrote:
>> Note that per-dev actions
>> can still be specified at port-level and it has the same effect of
>> specifying the action for all devices on the port.
>>
> 
> Why not use eh_info->action for port-level only, and eh_info->dev_action
> [] for device-level only?
>>From my understanding, this clear separation can at least make code easy
> to read.

The distinction between port-wide (later it becomes link-wide) and 
device-wide EH operations is meaningful only for PATA devices.  For a 
SATA LLD, device-wide operations is port-wide operation and using 
different fields doesn't make much sense.

So, I chose to put a bit more complexity where those per-dev actions are 
implemented while allowing LLDs and other parts of EH not to distinguish 
between those two unless it specifically wants to.

-- 
tejun

  reply	other threads:[~2006-06-20  8:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-19  9:27 [PATCH] libata: implement per-dev EH action mask eh_info->dev_action[] Tejun Heo
2006-06-20  7:02 ` zhao, forrest
2006-06-20  8:08   ` Tejun Heo [this message]
2006-06-23  3:37 ` 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=4497AD00.6000703@gmail.com \
    --to=htejun@gmail.com \
    --cc=forrest.zhao@intel.com \
    --cc=jgarzik@pobox.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).