From: josh@joshtriplett.org
To: Rashika Kheria <rashika.kheria@gmail.com>
Cc: linux-kernel@vger.kernel.org,
"Nicholas A. Bellinger" <nab@linux-iscsi.org>,
linux-scsi@vger.kernel.org, target-devel@vger.kernel.org
Subject: Re: [PATCH 1/4] drivers: target: Move prototype declaration of function to header file target_core_pr.h
Date: Wed, 18 Dec 2013 10:37:41 -0800 [thread overview]
Message-ID: <20131218183741.GA24229@cloud> (raw)
In-Reply-To: <1a63603bc5ff05147c419a301d59b135cd0c8406.1387390091.git.rashika.kheria@gmail.com>
On Wed, Dec 18, 2013 at 11:54:32PM +0530, Rashika Kheria wrote:
> Move prototype declaration of function
> spc_parse_naa_6h_vendor_specific() from target_core_xcopy.c to header
> file target_core_pr.h because it is used by more than one file.
>
> This eliminates the following warning in target_core_spc.c:
> drivers/target/target_core_spc.c:138:6: warning: no previous prototype for ‘spc_parse_naa_6h_vendor_specific’ [-Wmissing-prototypes]
>
> Signed-off-by: Rashika Kheria <rashika.kheria@gmail.com>
Reviewed-by: Josh Triplett <josh@joshtriplett.org>
> drivers/target/target_core_pr.h | 5 +++++
> drivers/target/target_core_xcopy.c | 4 ----
> 2 files changed, 5 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/target/target_core_pr.h b/drivers/target/target_core_pr.h
> index ed75cdd..2ee2936 100644
> --- a/drivers/target/target_core_pr.h
> +++ b/drivers/target/target_core_pr.h
> @@ -43,6 +43,11 @@
> #define PR_APTPL_MAX_IPORT_LEN 256
> #define PR_APTPL_MAX_TPORT_LEN 256
>
> +/*
> + * Function defined in target_core_spc.c
> + */
> +void spc_parse_naa_6h_vendor_specific(struct se_device *, unsigned char *);
> +
> extern struct kmem_cache *t10_pr_reg_cache;
>
> extern void core_pr_dump_initiator_port(struct t10_pr_registration *,
> diff --git a/drivers/target/target_core_xcopy.c b/drivers/target/target_core_xcopy.c
> index 6b88a99..669c536 100644
> --- a/drivers/target/target_core_xcopy.c
> +++ b/drivers/target/target_core_xcopy.c
> @@ -40,10 +40,6 @@
>
> static struct workqueue_struct *xcopy_wq = NULL;
> /*
> - * From target_core_spc.c
> - */
> -extern void spc_parse_naa_6h_vendor_specific(struct se_device *, unsigned char *);
> -/*
> * From target_core_device.c
> */
> extern struct mutex g_device_mutex;
> --
> 1.7.9.5
>
next prev parent reply other threads:[~2013-12-18 18:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-18 18:24 [PATCH 1/4] drivers: target: Move prototype declaration of function to header file target_core_pr.h Rashika Kheria
2013-12-18 18:26 ` [PATCH 2/4] drivers: target: Mark function as static in target_core_iblock.c Rashika Kheria
2013-12-18 18:38 ` josh
2013-12-19 0:11 ` Nicholas A. Bellinger
2013-12-18 18:32 ` [PATCH 3/4] drivers: target: Mark functions as static in tcm_loop.c Rashika Kheria
2013-12-18 18:39 ` josh
2013-12-19 0:11 ` Nicholas A. Bellinger
2013-12-18 18:35 ` [PATCH 4/4] drivers: target: Mark functions and structures as static in tfc_conf.c Rashika Kheria
2013-12-18 18:40 ` josh
2013-12-19 0:12 ` Nicholas A. Bellinger
2013-12-18 18:37 ` josh [this message]
2013-12-19 0:11 ` [PATCH 1/4] drivers: target: Move prototype declaration of function to header file target_core_pr.h Nicholas A. Bellinger
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=20131218183741.GA24229@cloud \
--to=josh@joshtriplett.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=nab@linux-iscsi.org \
--cc=rashika.kheria@gmail.com \
--cc=target-devel@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