From: "Rakib Mullick" <rakib.mullick@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: "Ingo Molnar" <mingo@elte.hu>,
"Andrew Morton" <akpm@linux-foundation.org>
Subject: Re: [PATCH] resource.c: Fixing section mismatch warning .
Date: Thu, 30 Oct 2008 10:01:53 +0600 [thread overview]
Message-ID: <b9df5fa10810292101o4ac4a67n77681a198b06311d@mail.gmail.com> (raw)
In-Reply-To: <b9df5fa10810292035p4c5a70eay44efae337a38d067@mail.gmail.com>
On 10/30/08, Rakib Mullick <rakib.mullick@gmail.com> wrote:
> LD kernel/built-in.o
> WARNING: kernel/built-in.o(.text+0xfcad): Section mismatch in
> reference from the function reserve_region_with_split() to the
> function .init.text:__reserve_region_with_split()
> The function reserve_region_with_split() references
> the function __init __reserve_region_with_split().
> This is often because reserve_region_with_split lacks a __init
> annotation or the annotation of __reserve_region_with_split is wrong.
>
> This patch fixes the above warning.
>
I'm sorry. This problem has been fixed. I should've check this before
sending this patch.
Again, sorry.
> Thanks.
>
> Signed-off-by: Md.Rakib H. Mullick <rakib.mullick@gmail.com>
>
> --- linux-2.6-orig/kernel/resource.c 2008-10-28 20:52:38.000000000 +0600
> +++ linux-2.6/kernel/resource.c 2008-10-28 22:34:44.000000000 +0600
> @@ -571,7 +571,7 @@ static void __init __reserve_region_with
>
> }
>
> -void reserve_region_with_split(struct resource *root,
> +void __init reserve_region_with_split(struct resource *root,
> resource_size_t start, resource_size_t end,
> const char *name)
> {
>
prev parent reply other threads:[~2008-10-30 4:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-30 3:35 Rakib Mullick
2008-10-30 4:01 ` Rakib Mullick [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=b9df5fa10810292101o4ac4a67n77681a198b06311d@mail.gmail.com \
--to=rakib.mullick@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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®