mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Nicholas A. Bellinger" <nab@linux-iscsi.org>
To: Axel Lin <axel.lin@gmail.com>
Cc: linux-kernel@vger.kernel.org,
	James Bottomley <James.Bottomley@suse.de>,
	linux-scsi <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH] [SCSI] target: Add __init/__exit annotation for target_core_init_configfs/target_core_exit_configfs
Date: Sun, 06 Mar 2011 22:44:33 -0800	[thread overview]
Message-ID: <1299480273.19683.201.camel@haakon2.linux-iscsi.org> (raw)
In-Reply-To: <1299467950.4791.1.camel@mola>

On Mon, 2011-03-07 at 11:19 +0800, Axel Lin wrote:
> This patch fixes below section mismatch warning.
> WARNING: vmlinux.o(.text+0x21617a): Section mismatch in reference from the function target_core_init_configfs() to the function .init.text:rd_module_init()
> The function target_core_init_configfs() references
> the function __init rd_module_init().
> This is often because target_core_init_configfs lacks a __init
> annotation or the annotation of rd_module_init is wrong.
> 
> Signed-off-by: Axel Lin <axel.lin@gmail.com>
> ---
>  drivers/target/target_core_configfs.c |    4 ++--
>  1 files changed, 2 insertions(+), 2 deletions(-)
> 

Hi Axel,

I have committed this patch with a few minor commit-log cleanups into
lio-core-2.6.git/lio-4.1 here:

Created commit dbb7295:: target: Add __init/__exit annotation for target_core_[init,exit]_configfs
 1 files changed, 2 insertions(+), 2 deletions(-)

This will get cherry-picked into lio v4.0 branches shortly, and I will
queue up as a for-39 mainline fix.

Thanks for your patch!

--nab

> diff --git a/drivers/target/target_core_configfs.c b/drivers/target/target_core_configfs.c
> index caf8dc1..378835e 100644
> --- a/drivers/target/target_core_configfs.c
> +++ b/drivers/target/target_core_configfs.c
> @@ -3044,7 +3044,7 @@ static struct config_item_type target_core_cit = {
>  
>  /* Stop functions for struct config_item_type target_core_hba_cit */
>  
> -static int target_core_init_configfs(void)
> +static int __init target_core_init_configfs(void)
>  {
>  	struct config_group *target_cg, *hba_cg = NULL, *alua_cg = NULL;
>  	struct config_group *lu_gp_cg = NULL;
> @@ -3176,7 +3176,7 @@ out_global:
>  	return -1;
>  }
>  
> -static void target_core_exit_configfs(void)
> +static void __exit target_core_exit_configfs(void)
>  {
>  	struct configfs_subsystem *subsys;
>  	struct config_group *hba_cg, *alua_cg, *lu_gp_cg;


      reply	other threads:[~2011-03-07  6:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-07  3:19 Axel Lin
2011-03-07  6:44 ` Nicholas A. Bellinger [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=1299480273.19683.201.camel@haakon2.linux-iscsi.org \
    --to=nab@linux-iscsi.org \
    --cc=James.Bottomley@suse.de \
    --cc=axel.lin@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.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

all inboxes | Powered by JetHome®