From: Ryosuke Saito <raitosyo@gmail.com>
To: dwmw2@infradead.org
Cc: robert.jarzmik@free.fr, mikedunn@newsguy.com,
ivan.djelic@parrot.com, artem.bityutskiy@linux.intel.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mtd: fix section mismatch for doc_probe_device
Date: Thu, 15 Mar 2012 19:04:25 +0900 [thread overview]
Message-ID: <CADTWAOLcFnZThjvXNSO2uba2vDU4DG48gmQQsYL7GPPbO8rTpg@mail.gmail.com> (raw)
In-Reply-To: <CADTWAO+=Zu6EtzTxm3j50f29HATekCfXuwgGeK=m0Zrw5Ljjig@mail.gmail.com>
Sorry, please ignore it.
I will re-send a plain text message.
Best regards,
Ryosuke
On Thu, Mar 15, 2012 at 6:24 PM, Ryosuke Saito <raitosyo@gmail.com> wrote:
> doc_probe_device() is only called from docg3_probe() which is in .init.text,
> so it must be in the same section to avoid a section mismatch warning.
>
> Signed-off-by: Ryosuke Saito <raitosyo@gmail.com>
> ---
> drivers/mtd/devices/docg3.c | 4 ++--
> 1 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/mtd/devices/docg3.c b/drivers/mtd/devices/docg3.c
> index 25f688c..db9a4b7 100644
> --- a/drivers/mtd/devices/docg3.c
> +++ b/drivers/mtd/devices/docg3.c
> @@ -1846,8 +1846,8 @@ static void __init doc_set_driver_info(int chip_id,
> struct mtd_info *mtd)
> * if a memory allocation failed. If floor 0 is checked, a reset of the
> ASIC is
> * launched.
> */
> -static struct mtd_info *doc_probe_device(void __iomem *base, int floor,
> - struct device *dev)
> +static struct mtd_info * __init
> +doc_probe_device(void __iomem *base, int floor, struct device *dev)
> {
> int ret, bbt_nbpages;
> u16 chip_id, chip_id_inv;
parent reply other threads:[~2012-03-15 10:04 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <CADTWAO+=Zu6EtzTxm3j50f29HATekCfXuwgGeK=m0Zrw5Ljjig@mail.gmail.com>]
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=CADTWAOLcFnZThjvXNSO2uba2vDU4DG48gmQQsYL7GPPbO8rTpg@mail.gmail.com \
--to=raitosyo@gmail.com \
--cc=artem.bityutskiy@linux.intel.com \
--cc=dwmw2@infradead.org \
--cc=ivan.djelic@parrot.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mikedunn@newsguy.com \
--cc=robert.jarzmik@free.fr \
/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®