linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Tirumalesh Chalamarla <tchalamarla@caviumnetworks.com>
Cc: stripathi@apm.com, linux-ide@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH V2] AHCI: Workaround for ThunderX Errata#22536
Date: Mon, 15 Feb 2016 13:30:41 -0500	[thread overview]
Message-ID: <20160215183041.GH3965@htj.duckdns.org> (raw)
In-Reply-To: <56C147B2.9010303@caviumnetworks.com>

Hello, Tirumalesh.

On Sun, Feb 14, 2016 at 07:36:18PM -0800, Tirumalesh Chalamarla wrote:
> There is no need for special Driver, AHCI is sufficient for ThunderX, the
> file only contains this interrupt handler,
> is it preferable if this interrupt handler in libahci.c with others, instead
> of separate file?

Yeap, just fold it in ahci.c with surrounding #ifdef guard.

Thanks.

-- 
tejun

  reply	other threads:[~2016-02-15 18:30 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-12 23:20 [PATCH V2] AHCI: Workaround for ThunderX Errata#22536 tchalamarla
2016-02-13 16:54 ` Sergei Shtylyov
2016-02-14 17:01 ` Tejun Heo
2016-02-15  3:36   ` Tirumalesh Chalamarla
2016-02-15 18:30     ` Tejun Heo [this message]
2016-02-16 14:42       ` Robert Richter
2016-02-16 19:14         ` Tirumalesh Chalamarla
2016-02-16 19:38           ` David Daney
2016-02-16 19:50             ` Tirumalesh Chalamarla
2016-02-16 21:14               ` Robert Richter
2016-02-16 23:13                 ` Tirumalesh Chalamarla
2016-02-17 11:29                   ` Will Deacon
2016-02-17 18:57                     ` David Daney
2016-02-17 20:00                       ` Tejun Heo
2016-02-17 21:46                         ` Tirumalesh Chalamarla

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=20160215183041.GH3965@htj.duckdns.org \
    --to=tj@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stripathi@apm.com \
    --cc=tchalamarla@caviumnetworks.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).