Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1721421 > unrolled thread
| Started by | Thorsten Leemhuis <regressions@leemhuis.info> |
|---|---|
| First post | 2017-08-28 11:30 +0200 |
| Last post | 2017-08-28 12:30 +0200 |
| Articles | 3 — 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] ACPI/IORT: fix build regression without IOMMU Thorsten Leemhuis <regressions@leemhuis.info> - 2017-08-28 11:30 +0200
Re: [PATCH] ACPI/IORT: fix build regression without IOMMU Lorenzo Pieralisi <lorenzo.pieralisi@arm.com> - 2017-08-28 12:00 +0200
Re: [PATCH] ACPI/IORT: fix build regression without IOMMU Thorsten Leemhuis <regressions@leemhuis.info> - 2017-08-28 12:30 +0200
| From | Thorsten Leemhuis <regressions@leemhuis.info> |
|---|---|
| Date | 2017-08-28 11:30 +0200 |
| Subject | Re: [PATCH] ACPI/IORT: fix build regression without IOMMU |
| Message-ID | <ujowN-3Qe-9@gated-at.bofh.it> |
On 10.08.2017 16:24, Lorenzo Pieralisi wrote:
> On Thu, Aug 10, 2017 at 02:11:00PM +0200, Arnd Bergmann wrote:
>> A recent change reintroduced a bug that had previously been
>> fixed by commit d49f2dedf33b ("ACPI/IORT: Fix CONFIG_IOMMU_API
>> dependency"):
>>
>> drivers/acpi/arm64/iort.c: In function 'iort_iommu_configure':
>> drivers/acpi/arm64/iort.c:829:26: error: 'struct iommu_fwspec' has no member named 'ops'
>>
>> This does the same change again, replacing another direct
>> reference to iommu_fwspec->ops with a helper function call.
>>
>> Fixes: bc8648d49a95 ("ACPI/IORT: Handle PCI aliases properly for IOMMUs")
>> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
>> ---
>> drivers/acpi/arm64/iort.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> Sorry Arnd, thanks, I will send it to Catalin straight away.
Was there any progress? Afaics that patch hasn't hit mainline yet (or
was it fixed by a different patch?). Asking because the issue is
mentioned in the regression report for 4.13.
Ciao, Thorsten
[toc] | [next] | [standalone]
| From | Lorenzo Pieralisi <lorenzo.pieralisi@arm.com> |
|---|---|
| Date | 2017-08-28 12:00 +0200 |
| Message-ID | <ujoZQ-3ZF-11@gated-at.bofh.it> |
| In reply to | #1721421 |
On Mon, Aug 28, 2017 at 11:27:20AM +0200, Thorsten Leemhuis wrote:
> On 10.08.2017 16:24, Lorenzo Pieralisi wrote:
> > On Thu, Aug 10, 2017 at 02:11:00PM +0200, Arnd Bergmann wrote:
> >> A recent change reintroduced a bug that had previously been
> >> fixed by commit d49f2dedf33b ("ACPI/IORT: Fix CONFIG_IOMMU_API
> >> dependency"):
> >>
> >> drivers/acpi/arm64/iort.c: In function 'iort_iommu_configure':
> >> drivers/acpi/arm64/iort.c:829:26: error: 'struct iommu_fwspec' has no member named 'ops'
> >>
> >> This does the same change again, replacing another direct
> >> reference to iommu_fwspec->ops with a helper function call.
> >>
> >> Fixes: bc8648d49a95 ("ACPI/IORT: Handle PCI aliases properly for IOMMUs")
> >> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
> >> ---
> >> drivers/acpi/arm64/iort.c | 2 +-
> >> 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > Sorry Arnd, thanks, I will send it to Catalin straight away.
>
> Was there any progress? Afaics that patch hasn't hit mainline yet (or
> was it fixed by a different patch?). Asking because the issue is
> mentioned in the regression report for 4.13.
I do not understand how it can be mentioned in the 4.13 regression
report given that it is code queued for 4.14 and it is not in the
mainline that triggered the regression. Anyway, fix is queued along
with other patches and it is in -next (coming from arm64 tree):
commit: 4d36037a9a07
Does this answer your question ?
Lorenzo
[toc] | [prev] | [next] | [standalone]
| From | Thorsten Leemhuis <regressions@leemhuis.info> |
|---|---|
| Date | 2017-08-28 12:30 +0200 |
| Message-ID | <ujpsR-4p8-5@gated-at.bofh.it> |
| In reply to | #1721456 |
Lo! On 28.08.2017 11:57, Lorenzo Pieralisiwrote: > On Mon, Aug 28, 2017 at 11:27:20AM +0200, Thorsten Leemhuis wrote: > >> Was there any progress? Afaics that patch hasn't hit mainline yet (or >> was it fixed by a different patch?). Asking because the issue is >> mentioned in the regression report for 4.13. > I do not understand how it can be mentioned in the 4.13 regression > report given that it is code queued for 4.14 […] Ohh, there is a simple explanation: Because I'm stupid and missed that the commit Arnd mentioned was not in mainline :-/ I could have sworn I checked that, but seems I did not. Sorry for the noise & many thx for the answer! Ciao, Thorsten
[toc] | [prev] | [standalone]
Back to top | Article view | linux.kernel
csiph-web