From: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
To: will.deacon@arm.com, catalin.marinas@arm.com
Cc: hanjun.guo@linaro.org, dan.carpenter@oracle.com,
okaya@codeaurora.org, linux-arm-kernel@lists.infradead.org,
linux-acpi@vger.kernel.org
Subject: [GIT PULL] ACPI IORT fixes for v4.10-rc8
Date: Mon, 6 Feb 2017 13:38:56 +0000 [thread overview]
Message-ID: <20170206133856.GA14139@red-moon> (raw)
Hi Will, Catalin,
please consider pulling a couple of minor ACPI IORT fixes that were
missed in the last few -rc* cycles but should be considered for
merging as soon as possible, hopefully before v4.10 is released.
Thanks,
Lorenzo
The following changes since commit d5adbfcd5f7bcc6fa58a41c5c5ada0e5c826ce2c:
Linux 4.10-rc7 (2017-02-05 15:10:58 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/lpieralisi/linux.git tags/iort-fixes-for-v4.10
for you to fetch changes up to 2a42d9d5dd259b0bdef34a00da426ac5fb0261e1:
ACPI/IORT: Fix the error return code in iort_add_smmu_platform_device() (2017-02-06 12:50:53 +0000)
----------------------------------------------------------------
IORT fixes as a fall-out from IORT SMMU changes:
* Fix return value when IORT code allocating platform
devices fails, that is causing a successful return
on failure
* Fix the indexing in iort_node_get_id() so that the correct
mapping entry is used to return the correct IORT parent
node resulting from the mapping
----------------------------------------------------------------
Dan Carpenter (1):
ACPI/IORT: Fix the error return code in iort_add_smmu_platform_device()
Lorenzo Pieralisi (1):
ACPI/IORT: Fix iort_node_get_id() mapping entries indexing
drivers/acpi/arm64/iort.c | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
next reply other threads:[~2017-02-06 13:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-06 13:38 Lorenzo Pieralisi [this message]
2017-02-06 13:47 ` [GIT PULL] ACPI IORT fixes for v4.10-rc8 Will Deacon
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=20170206133856.GA14139@red-moon \
--to=lorenzo.pieralisi@arm.com \
--cc=catalin.marinas@arm.com \
--cc=dan.carpenter@oracle.com \
--cc=hanjun.guo@linaro.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=okaya@codeaurora.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).