From: "Jörg Rödel" <joro@8bytes.org>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: Borislav Petkov <bp@alien8.de>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
Lv Zheng <lv.zheng@intel.com>, Bob Moore <robert.moore@intel.com>,
lkml <linux-kernel@vger.kernel.org>,
Linux ACPI <linux-acpi@vger.kernel.org>
Subject: Re: 174cc7187e6f ACPICA: Tables: Back port acpi_get_table_with_size() and early_acpi_os_unmap_memory() from Linux kernel
Date: Mon, 9 Jan 2017 11:52:26 +0100 [thread overview]
Message-ID: <20170109105226.GR17255@8bytes.org> (raw)
In-Reply-To: <CAJZ5v0idFBHG=OKRiBqvsYPgUrWQsqjTKYXfKxfdG023qsCbkw@mail.gmail.com>
Hi Rafael,
On Sun, Jan 08, 2017 at 03:20:20AM +0100, Rafael J. Wysocki wrote:
> ---
> drivers/iommu/amd_iommu_init.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> Index: linux-pm/drivers/iommu/amd_iommu_init.c
> ===================================================================
> --- linux-pm.orig/drivers/iommu/amd_iommu_init.c
> +++ linux-pm/drivers/iommu/amd_iommu_init.c
> @@ -2230,7 +2230,7 @@ static int __init early_amd_iommu_init(v
> */
> ret = check_ivrs_checksum(ivrs_base);
> if (ret)
> - return ret;
> + goto out;
>
> amd_iommu_target_ivhd_type = get_highest_supported_ivhd_type(ivrs_base);
> DUMP_printk("Using IVHD type %#x\n", amd_iommu_target_ivhd_type);
Yeah, good catch. Can you send me a patch for this and I am going to
send the fix upstream asap.
Thanks,
Joerg
next prev parent reply other threads:[~2017-01-09 10:52 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20170107204227.bwdb5yzrjpiggkmo@pd.tnic>
2017-01-07 23:30 ` 174cc7187e6f ACPICA: Tables: Back port acpi_get_table_with_size() and early_acpi_os_unmap_memory() from Linux kernel Rafael J. Wysocki
2017-01-08 0:07 ` Borislav Petkov
2017-01-08 0:22 ` Rafael J. Wysocki
2017-01-08 0:37 ` Borislav Petkov
2017-01-08 0:52 ` Rafael J. Wysocki
2017-01-08 1:01 ` Borislav Petkov
2017-01-08 1:45 ` Rafael J. Wysocki
2017-01-08 2:20 ` Rafael J. Wysocki
2017-01-08 13:03 ` Borislav Petkov
2017-01-09 1:58 ` Zheng, Lv
2017-01-09 2:36 ` Zheng, Lv
2017-01-09 9:33 ` Borislav Petkov
2017-01-09 22:18 ` Paul E. McKenney
2017-01-09 22:25 ` Rafael J. Wysocki
2017-01-09 23:14 ` Paul E. McKenney
2017-01-09 23:15 ` Borislav Petkov
2017-01-09 23:32 ` Paul E. McKenney
2017-01-09 23:40 ` Borislav Petkov
2017-01-09 23:52 ` Paul E. McKenney
2017-01-09 23:52 ` Borislav Petkov
2017-01-10 0:44 ` Zheng, Lv
2017-01-10 1:27 ` Rafael J. Wysocki
2017-01-10 2:23 ` Paul E. McKenney
2017-01-10 5:41 ` Zheng, Lv
2017-01-10 5:51 ` Paul E. McKenney
2017-01-11 9:21 ` Borislav Petkov
2017-01-11 9:51 ` Paul E. McKenney
2017-01-11 10:03 ` Borislav Petkov
2017-01-11 10:22 ` Paul E. McKenney
2017-01-10 9:41 ` Borislav Petkov
2017-01-11 3:42 ` Rafael J. Wysocki
2017-01-11 9:42 ` Borislav Petkov
2017-01-09 23:42 ` Rafael J. Wysocki
2017-01-10 0:21 ` Paul E. McKenney
2017-01-09 5:21 ` Zheng, Lv
2017-01-09 10:52 ` Jörg Rödel [this message]
2017-01-09 22:41 ` Rafael J. Wysocki
2017-01-09 22:57 ` Borislav Petkov
2017-01-10 13:58 ` Jörg Rödel
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=20170109105226.GR17255@8bytes.org \
--to=joro@8bytes.org \
--cc=bp@alien8.de \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lv.zheng@intel.com \
--cc=rafael.j.wysocki@intel.com \
--cc=rafael@kernel.org \
--cc=robert.moore@intel.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