From: Thorsten Leemhuis <regressions@leemhuis.info>
To: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
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 12:23:05 +0200 [thread overview]
Message-ID: <a67c6a9b-9ea0-ac44-9aaa-5a6747b2e8b1@leemhuis.info> (raw)
In-Reply-To: <20170828095759.GB8471@e107981-lin.cambridge.arm.com>
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
prev parent reply other threads:[~2017-08-28 10:23 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
2017-08-28 10:23 ` Thorsten Leemhuis [this message]
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=a67c6a9b-9ea0-ac44-9aaa-5a6747b2e8b1@leemhuis.info \
--to=regressions@leemhuis.info \
--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=lorenzo.pieralisi@arm.com \
--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®