From: Joerg Roedel <joerg.roedel-5C7GfCeVMHo@public.gmane.org>
To: Jan Beulich <JBeulich-IBi9RG/b67k@public.gmane.org>
Cc: iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org
Subject: Re: [PATCH] AMD IOMMU: iommu_set_device_table() must not be __init
Date: Thu, 8 Mar 2012 11:38:13 +0100 [thread overview]
Message-ID: <20120308103813.GP10684@amd.com> (raw)
In-Reply-To: <4F5882B502000078000770CE-ce6RLXgGx+vWGUEhTRrCg1aTQe2KTcn/@public.gmane.org>
On Thu, Mar 08, 2012 at 08:58:13AM +0000, Jan Beulich wrote:
> This function is called from enable_iommus(), which in turn is used
> from amd_iommu_resume().
>
> Signed-off-by: Jan Beulich <jbeulich-IBi9RG/b67k@public.gmane.org>
>
> ---
> drivers/iommu/amd_iommu_init.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> --- 3.3-rc6/drivers/iommu/amd_iommu_init.c
> +++ 3.3-rc6-amd-iommu-sections/drivers/iommu/amd_iommu_init.c
> @@ -275,7 +275,7 @@ static void iommu_set_exclusion_range(st
> }
>
> /* Programs the physical address of the device table into the IOMMU hardware */
> -static void __init iommu_set_device_table(struct amd_iommu *iommu)
> +static void iommu_set_device_table(struct amd_iommu *iommu)
> {
> u64 entry;
Applied to iommu/fixes, thanks Jan.
--
AMD Operating System Research Center
Advanced Micro Devices GmbH Einsteinring 24 85609 Dornach
General Managers: Alberto Bozzo
Registration: Dornach, Landkr. Muenchen; Registerger. Muenchen, HRB Nr. 43632
prev parent reply other threads:[~2012-03-08 10:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-08 8:58 [PATCH] AMD IOMMU: iommu_set_device_table() must not be __init Jan Beulich
[not found] ` <4F5882B502000078000770CE-ce6RLXgGx+vWGUEhTRrCg1aTQe2KTcn/@public.gmane.org>
2012-03-08 10:38 ` Joerg Roedel [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=20120308103813.GP10684@amd.com \
--to=joerg.roedel-5c7gfcevmho@public.gmane.org \
--cc=JBeulich-IBi9RG/b67k@public.gmane.org \
--cc=iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
/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).