linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Ondrej Zary <linux@rainbow-software.org>
Cc: linux-ide@vger.kernel.org, Joseph Chan <JosephChan@via.com.tw>,
	Kernel development list <linux-kernel@vger.kernel.org>
Subject: Re: [RFC PATCH] sata_via: Apply WD workaround only when needed
Date: Wed, 17 Feb 2016 12:51:55 -0500	[thread overview]
Message-ID: <20160217175155.GA2626@mtj.duckdns.org> (raw)
In-Reply-To: <201602162357.52647.linux@rainbow-software.org>

Hello,

On Tue, Feb 16, 2016 at 11:57:52PM +0100, Ondrej Zary wrote:
> Guess that I need to read SErr manually?

Yeah, read whatever is necessary.  It's restricted to the controller
anyway.

Thanks.

-- 
tejun

      reply	other threads:[~2016-02-17 17:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-15 21:01 [RFC PATCH] sata_via: Apply WD workaround only when needed Ondrej Zary
2016-02-16 21:42 ` Tejun Heo
2016-02-16 22:57   ` Ondrej Zary
2016-02-17 17:51     ` Tejun Heo [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=20160217175155.GA2626@mtj.duckdns.org \
    --to=tj@kernel.org \
    --cc=JosephChan@via.com.tw \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@rainbow-software.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).