From: Joerg Roedel <joro-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
To: Emil Medve <Emilian.Medve-eDlz3WWmN0ll57MIdRCFDg@public.gmane.org>
Cc: Varun.Sethi-eDlz3WWmN0ll57MIdRCFDg@public.gmane.org,
iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org,
jroedel-l3A5Bk7waGM@public.gmane.org
Subject: Re: [PATCH v2 1/3] iommu/fsl: Fix section mismatch
Date: Mon, 26 Jan 2015 13:49:53 +0100 [thread overview]
Message-ID: <20150126124953.GF4653@8bytes.org> (raw)
In-Reply-To: <1421938042-22580-1-git-send-email-Emilian.Medve-eDlz3WWmN0ll57MIdRCFDg@public.gmane.org>
On Thu, Jan 22, 2015 at 08:47:20AM -0600, Emil Medve wrote:
> Section mismatch in reference from the variable fsl_of_pamu_driver to the function .init.text:fsl_pamu_probe()
> The variable fsl_of_pamu_driver references
> the function __init fsl_pamu_probe()
> If the reference is valid then annotate the
> variable with __init* or __refdata (see linux/init.h) or name the variable:
> *_template, *_timer, *_sht, *_ops, *_probe, *_probe_one, *_console
>
> Signed-off-by: Emil Medve <Emilian.Medve-eDlz3WWmN0ll57MIdRCFDg@public.gmane.org>
Applied patch 1 and 2 to ppc/pamu, thanks.
prev parent reply other threads:[~2015-01-26 12:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-22 14:47 [PATCH v2 1/3] iommu/fsl: Fix section mismatch Emil Medve
[not found] ` <1421938042-22580-1-git-send-email-Emilian.Medve-eDlz3WWmN0ll57MIdRCFDg@public.gmane.org>
2015-01-22 14:47 ` [PATCH 2/3] iommu/fsl: Remove unused fsl_of_pamu_ids[] Emil Medve
[not found] ` <1421938042-22580-2-git-send-email-Emilian.Medve-eDlz3WWmN0ll57MIdRCFDg@public.gmane.org>
2015-01-23 6:15 ` Varun Sethi
2015-01-22 14:47 ` [PATCH 3/3] iommu/fsl: Sprinkle some __init* annotations Emil Medve
[not found] ` <1421938042-22580-3-git-send-email-Emilian.Medve-eDlz3WWmN0ll57MIdRCFDg@public.gmane.org>
2015-01-23 6:11 ` Varun Sethi
2015-01-23 6:12 ` [PATCH v2 1/3] iommu/fsl: Fix section mismatch Varun Sethi
2015-01-26 12:49 ` 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=20150126124953.GF4653@8bytes.org \
--to=joro-zlv9swrftaidnm+yrofe0a@public.gmane.org \
--cc=Emilian.Medve-eDlz3WWmN0ll57MIdRCFDg@public.gmane.org \
--cc=Varun.Sethi-eDlz3WWmN0ll57MIdRCFDg@public.gmane.org \
--cc=iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=jroedel-l3A5Bk7waGM@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