From: Tirumalesh Chalamarla <tchalamarla@caviumnetworks.com>
To: Tejun Heo <tj@kernel.org>, David Daney <ddaney@caviumnetworks.com>
Cc: Will Deacon <will.deacon@arm.com>,
stripathi@apm.com, linux-kernel@vger.kernel.org,
linux-ide@vger.kernel.org, Robert Richter <rric@kernel.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH V2] AHCI: Workaround for ThunderX Errata#22536
Date: Wed, 17 Feb 2016 13:46:47 -0800 [thread overview]
Message-ID: <56C4EA47.6010908@caviumnetworks.com> (raw)
In-Reply-To: <20160217200029.GB4751@mtj.duckdns.org>
On 02/17/2016 12:00 PM, Tejun Heo wrote:
> Hello, David.
>
> On Wed, Feb 17, 2016 at 10:57:50AM -0800, David Daney wrote:
>> If the ahci/ata maintainers insist, we can add that.
>
> I don't mind whether it is CONFIG_ARM64 or something more specific but
> I think it's a good idea to gate it some way.
>
Already posted a V3, could you please comment on that.
Thanks,
Tirumalesh.
>> <sarcasm>
>
> If at all possible, please write plain arguments.
>
>> Should we also add some CONFIG_ variables for:
>>
>> ahci_mcp89_apple_enable()
>> ahci_sb600_enable_64bit()
>> ahci_p5wdh_workaround()
>
> And I think these should be gated behind CONFIG_X86. The lack of
> gating is historic, not intentional.
>
> Thanks.
>
WARNING: multiple messages have this Message-ID (diff)
From: tchalamarla@caviumnetworks.com (Tirumalesh Chalamarla)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V2] AHCI: Workaround for ThunderX Errata#22536
Date: Wed, 17 Feb 2016 13:46:47 -0800 [thread overview]
Message-ID: <56C4EA47.6010908@caviumnetworks.com> (raw)
In-Reply-To: <20160217200029.GB4751@mtj.duckdns.org>
On 02/17/2016 12:00 PM, Tejun Heo wrote:
> Hello, David.
>
> On Wed, Feb 17, 2016 at 10:57:50AM -0800, David Daney wrote:
>> If the ahci/ata maintainers insist, we can add that.
>
> I don't mind whether it is CONFIG_ARM64 or something more specific but
> I think it's a good idea to gate it some way.
>
Already posted a V3, could you please comment on that.
Thanks,
Tirumalesh.
>> <sarcasm>
>
> If at all possible, please write plain arguments.
>
>> Should we also add some CONFIG_ variables for:
>>
>> ahci_mcp89_apple_enable()
>> ahci_sb600_enable_64bit()
>> ahci_p5wdh_workaround()
>
> And I think these should be gated behind CONFIG_X86. The lack of
> gating is historic, not intentional.
>
> Thanks.
>
WARNING: multiple messages have this Message-ID (diff)
From: Tirumalesh Chalamarla <tchalamarla@caviumnetworks.com>
To: Tejun Heo <tj@kernel.org>, David Daney <ddaney@caviumnetworks.com>
Cc: Will Deacon <will.deacon@arm.com>, <stripathi@apm.com>,
<linux-kernel@vger.kernel.org>, <linux-ide@vger.kernel.org>,
Robert Richter <rric@kernel.org>,
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH V2] AHCI: Workaround for ThunderX Errata#22536
Date: Wed, 17 Feb 2016 13:46:47 -0800 [thread overview]
Message-ID: <56C4EA47.6010908@caviumnetworks.com> (raw)
In-Reply-To: <20160217200029.GB4751@mtj.duckdns.org>
On 02/17/2016 12:00 PM, Tejun Heo wrote:
> Hello, David.
>
> On Wed, Feb 17, 2016 at 10:57:50AM -0800, David Daney wrote:
>> If the ahci/ata maintainers insist, we can add that.
>
> I don't mind whether it is CONFIG_ARM64 or something more specific but
> I think it's a good idea to gate it some way.
>
Already posted a V3, could you please comment on that.
Thanks,
Tirumalesh.
>> <sarcasm>
>
> If at all possible, please write plain arguments.
>
>> Should we also add some CONFIG_ variables for:
>>
>> ahci_mcp89_apple_enable()
>> ahci_sb600_enable_64bit()
>> ahci_p5wdh_workaround()
>
> And I think these should be gated behind CONFIG_X86. The lack of
> gating is historic, not intentional.
>
> Thanks.
>
next prev parent reply other threads:[~2016-02-17 21:46 UTC|newest]
Thread overview: 38+ 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-12 23:20 ` tchalamarla
2016-02-12 23:20 ` tchalamarla at caviumnetworks.com
2016-02-13 16:54 ` Sergei Shtylyov
2016-02-13 16:54 ` Sergei Shtylyov
2016-02-14 17:01 ` Tejun Heo
2016-02-14 17:01 ` Tejun Heo
2016-02-15 3:36 ` Tirumalesh Chalamarla
2016-02-15 3:36 ` Tirumalesh Chalamarla
2016-02-15 3:36 ` Tirumalesh Chalamarla
2016-02-15 18:30 ` Tejun Heo
2016-02-15 18:30 ` Tejun Heo
2016-02-16 14:42 ` Robert Richter
2016-02-16 14:42 ` Robert Richter
2016-02-16 19:14 ` Tirumalesh Chalamarla
2016-02-16 19:14 ` Tirumalesh Chalamarla
2016-02-16 19:14 ` Tirumalesh Chalamarla
2016-02-16 19:38 ` David Daney
2016-02-16 19:38 ` David Daney
2016-02-16 19:38 ` David Daney
2016-02-16 19:50 ` Tirumalesh Chalamarla
2016-02-16 19:50 ` Tirumalesh Chalamarla
2016-02-16 19:50 ` Tirumalesh Chalamarla
2016-02-16 21:14 ` Robert Richter
2016-02-16 21:14 ` Robert Richter
2016-02-16 23:13 ` Tirumalesh Chalamarla
2016-02-16 23:13 ` Tirumalesh Chalamarla
2016-02-16 23:13 ` Tirumalesh Chalamarla
2016-02-17 11:29 ` Will Deacon
2016-02-17 11:29 ` Will Deacon
2016-02-17 18:57 ` David Daney
2016-02-17 18:57 ` David Daney
2016-02-17 18:57 ` David Daney
2016-02-17 20:00 ` Tejun Heo
2016-02-17 20:00 ` Tejun Heo
2016-02-17 21:46 ` Tirumalesh Chalamarla [this message]
2016-02-17 21:46 ` Tirumalesh Chalamarla
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=56C4EA47.6010908@caviumnetworks.com \
--to=tchalamarla@caviumnetworks.com \
--cc=ddaney@caviumnetworks.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rric@kernel.org \
--cc=stripathi@apm.com \
--cc=tj@kernel.org \
--cc=will.deacon@arm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.