Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1552888 > unrolled thread
| Started by | Christopher Covington <cov@codeaurora.org> |
|---|---|
| First post | 2017-01-06 16:50 +0100 |
| Last post | 2017-01-06 17:00 +0100 |
| Articles | 2 — 2 participants |
Back to article view | Back to linux.kernel
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: [PATCH v2 2/5] arm64: Work around Falkor erratum 1003 Christopher Covington <cov@codeaurora.org> - 2017-01-06 16:50 +0100
Re: [PATCH v2 2/5] arm64: Work around Falkor erratum 1003 Timur Tabi <timur@codeaurora.org> - 2017-01-06 17:00 +0100
| From | Christopher Covington <cov@codeaurora.org> |
|---|---|
| Date | 2017-01-06 16:50 +0100 |
| Subject | Re: [PATCH v2 2/5] arm64: Work around Falkor erratum 1003 |
| Message-ID | <sWEWe-3VU-35@gated-at.bofh.it> |
On 12/29/2016 06:08 PM, Timur Tabi wrote: > On 12/29/2016 04:43 PM, Christopher Covington wrote: >> +config QCOM_FALKOR_E1003_RESERVED_ASID >> + int >> + default 1 >> + depends on QCOM_FALKOR_ERRATUM_1003 > > Also, since this can't be changed via the menu, why bother putting it in? I put it in in response to review comments asking for the magic number to be clarified by a #define or variable. I could not find a suitably shared header between the files in question, so I used the Kconfig machinery to generate the #define. Cov -- Qualcomm Datacenter Technologies, Inc. as an affiliate of Qualcomm Technologies, Inc. Qualcomm Technologies, Inc. is a member of the Code Aurora Forum, a Linux Foundation Collaborative Project.
[toc] | [next] | [standalone]
| From | Timur Tabi <timur@codeaurora.org> |
|---|---|
| Date | 2017-01-06 17:00 +0100 |
| Message-ID | <sWF5U-3ZI-39@gated-at.bofh.it> |
| In reply to | #1552888 |
Christopher Covington wrote: >> > Also, since this can't be changed via the menu, why bother putting it in? > I put it in in response to review comments asking for the magic number to > be clarified by a #define or variable. I could not find a suitably shared > header between the files in question, so I used the Kconfig machinery to > generate the #define. I don't think that's the right approach. Kconfigs are not an alternative to header files. Is the ASID configurable? If you just put some text after the "int" then it because a menu option that the user can select and change. -- Sent by an employee of the Qualcomm Innovation Center, Inc. The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum, hosted by The Linux Foundation.
[toc] | [prev] | [standalone]
Back to top | Article view | linux.kernel
csiph-web