mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
To: Thorsten Leemhuis <regressions@leemhuis.info>
Cc: Arnd Bergmann <arnd@arndb.de>, Hanjun Guo <hanjun.guo@linaro.org>,
	Sudeep Holla <sudeep.holla@arm.com>,
	"Rafael J. Wysocki" <rjw@rjwysocki.net>,
	Len Brown <lenb@kernel.org>, Will Deacon <will.deacon@arm.com>,
	Tomasz Nowicki <tn@semihalf.com>, Joerg Roedel <jroedel@suse.de>,
	Sricharan R <sricharan@codeaurora.org>,
	Robin Murphy <robin.murphy@arm.com>,
	Geetha Sowjanya <geethasowjanya.akula@cavium.com>,
	linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ACPI/IORT: fix build regression without IOMMU
Date: Mon, 28 Aug 2017 10:57:59 +0100	[thread overview]
Message-ID: <20170828095759.GB8471@e107981-lin.cambridge.arm.com> (raw)
In-Reply-To: <3fe9e409-b505-f9af-63b7-02e91918db9d@leemhuis.info>

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

  reply	other threads:[~2017-08-28  9:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-10 12:11 Arnd Bergmann
2017-08-10 14:24 ` Lorenzo Pieralisi
2017-08-28  9:27   ` Thorsten Leemhuis
2017-08-28  9:57     ` Lorenzo Pieralisi [this message]
2017-08-28 10:23       ` Thorsten Leemhuis

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=20170828095759.GB8471@e107981-lin.cambridge.arm.com \
    --to=lorenzo.pieralisi@arm.com \
    --cc=arnd@arndb.de \
    --cc=geethasowjanya.akula@cavium.com \
    --cc=hanjun.guo@linaro.org \
    --cc=jroedel@suse.de \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=regressions@leemhuis.info \
    --cc=rjw@rjwysocki.net \
    --cc=robin.murphy@arm.com \
    --cc=sricharan@codeaurora.org \
    --cc=sudeep.holla@arm.com \
    --cc=tn@semihalf.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®