linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Frans Pop <elendil@planet.nl>
To: Martin Michlmayr <tbm@cyrius.com>
Cc: Mark Lord <liml@rtr.ca>,
	linux-arm@vger.kernel.org, linux-ide@vger.kernel.org,
	Saeed Bishara <saeed@marvell.com>, Nicolas Pitre <nico@cam.org>,
	Lennert Buytenhek <buytenh@wantstofly.org>
Subject: Re: [RFC][PATCH] sata-mv: add module parameter msq_blink_led to enable quirk for SOC
Date: Tue, 10 Mar 2009 17:47:07 +0100	[thread overview]
Message-ID: <200903101747.09276.elendil@planet.nl> (raw)
In-Reply-To: <20090310162803.GA9120@deprecation.cyrius.com>

On Tuesday 10 March 2009, Martin Michlmayr wrote:
> * Mark Lord <liml@rtr.ca> [2009-03-10 11:06]:
> > Saeed said the original patch should apply "for all devices besides
> > to the SOC", which I think means all GenIIe chip variants.
>
> Unfortunately, we're seeing the problem with the SoC...

AIUI the SoC _is_ a GenIIe chip variant. Mark is asking me to extend the 
code to the PCI-based GenIIe chips.

  parent reply	other threads:[~2009-03-10 16:47 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-26  9:24 [regression] sata_mv: harddisk activity led no longer responsive on QNAP TS-109 Frans Pop
2008-08-26 10:25 ` Frans Pop
2009-01-24 14:57   ` Mark Lord
2009-02-24  8:33     ` [RFC][PATCH] " Frans Pop
2009-02-24  9:33       ` saeed bishara
2009-03-01  7:59         ` Martin Michlmayr
2009-03-01 12:44           ` Frans Pop
2009-03-10 11:36       ` [RFC][PATCH] sata-mv: add module parameter msq_blink_led to enable quirk for SOC Frans Pop
2009-03-10 15:06         ` Mark Lord
2009-03-10 16:28           ` Martin Michlmayr
2009-03-10 16:40             ` Mark Lord
2009-03-10 16:47             ` Frans Pop [this message]
2009-03-10 17:09           ` Frans Pop
2008-08-26 14:03 ` [regression] sata_mv: harddisk activity led no longer responsive on QNAP TS-109 Mark Lord
2008-08-27 14:56   ` Martin Michlmayr
2008-08-27 17:06     ` saeed bishara

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=200903101747.09276.elendil@planet.nl \
    --to=elendil@planet.nl \
    --cc=buytenh@wantstofly.org \
    --cc=liml@rtr.ca \
    --cc=linux-arm@vger.kernel.org \
    --cc=linux-ide@vger.kernel.org \
    --cc=nico@cam.org \
    --cc=saeed@marvell.com \
    --cc=tbm@cyrius.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).