From: Corentin Chary <corentincj@iksaif.net>
To: Rakib Mullick <rakib.mullick@gmail.com>
Cc: acpi4asus-user@lists.sourceforge.net,
Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [Resend][PATCH] eeepc-laptop: Properly annote eeepc_enable_camera().
Date: Sat, 3 Oct 2009 09:20:18 +0200 [thread overview]
Message-ID: <200910030920.18591.corentincj@iksaif.net> (raw)
In-Reply-To: <b9df5fa10910022324u1d91b4d0oe051ef45dd347cbc@mail.gmail.com>
On Saturday 03 October 2009 08:24:53 Rakib Mullick wrote:
> Currently the annotation for function eeepc_enable_camera() is
> __init, and refers to a
> function eeepc_hotk_add() which is non-init. Use __devinit for both
> functions which is
> more appropriate and fixes a section mismatch warning.
>
> We were warned by the following warning:
>
> LD drivers/platform/x86/built-in.o
> WARNING: drivers/platform/x86/built-in.o(.text+0x12e1): Section
> mismatch in reference from the function eeepc_hotk_add() to the
> function .init.text:eeepc_enable_camera()
> The function eeepc_hotk_add() references
> the function __init eeepc_enable_camera().
> This is often because eeepc_hotk_add lacks a __init
> annotation or the annotation of eeepc_enable_camera is wrong.
>
> ---
> Signed-off-by: Rakib Mullick <rakib.mullick@gmail.com>
>
> --- linus/drivers/platform/x86/eeepc-laptop.c 2009-10-03
> 12:44:40.000000000 +0600
> +++ rakib/drivers/platform/x86/eeepc-laptop.c 2009-10-03
> 12:48:42.000000000 +0600
> @@ -350,7 +350,7 @@ static const struct rfkill_ops eeepc_rfk
> .set_block = eeepc_rfkill_set,
> };
>
> -static void __init eeepc_enable_camera(void)
> +static void __devinit eeepc_enable_camera(void)
> {
> /*
> * If the following call to set_acpi() fails, it's because there's no
> @@ -1189,7 +1189,7 @@ static int eeepc_input_init(struct devic
> return 0;
> }
>
> -static int eeepc_hotk_add(struct acpi_device *device)
> +static int __devinit eeepc_hotk_add(struct acpi_device *device)
> {
> struct device *dev;
> int result;
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
Hi,
The patch is broken again,
The section
> --- linus/drivers/platform/x86/eeepc-laptop.c 2009-10-03
> 12:44:40.000000000 +0600
> +++ rakib/drivers/platform/x86/eeepc-laptop.c 2009-10-03
> 12:48:42.000000000 +0600
is line-wrapped by mail client when you send it. It happens because
rakib/drivers/platform/x86/eeepc-laptop.c is a very long patch.
The Signed-off-by also should be before ---
Anyway I fixed it and applied your patch in acpi4asus tree.
I'll try to get it merged into 2.6.32.
Please read Documentation/email-clients.txt to fix your mail client
or just use git send-email.
Thanks,
--
Corentin Chary
http://xf.iksaif.net
prev parent reply other threads:[~2009-10-03 7:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-03 6:24 Rakib Mullick
2009-10-03 7:20 ` Corentin Chary [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=200910030920.18591.corentincj@iksaif.net \
--to=corentincj@iksaif.net \
--cc=acpi4asus-user@lists.sourceforge.net \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rakib.mullick@gmail.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
all inboxes | Powered by JetHome®