From: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
To: Adithya K <linux.challenge1@gmail.com>
Cc: forest@alittletooquiet.net, gregkh@linuxfoundation.org,
tvboxspy@gmail.com, gclement@baobob.org, joe@perches.com,
guido@vanguardiasur.com.ar, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org,
Adithya Krishnamurthy <linux.challenge@gmail.com>
Subject: Re: [PATCH 1/1] [PATCH] Staging:vt6655: sparse warning fix
Date: Tue, 9 Dec 2014 18:04:25 +0530 [thread overview]
Message-ID: <20141209123425.GA5407@sudip-PC> (raw)
In-Reply-To: <1418061805-19768-1-git-send-email-linux.challenge1@gmail.com>
On Mon, Dec 08, 2014 at 11:33:25PM +0530, Adithya K wrote:
> From: Adithya Krishnamurthy <linux.challenge@gmail.com>
>
> Fixed sparse warning fix.
you should mention what type of warning you have fixed.
sudip
>
> Signed-off-by: Adithya Krishnamurthy <linux.challenge1@gmail.com>
> ---
> ---
> drivers/staging/vt6655/device_main.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/staging/vt6655/device_main.c b/drivers/staging/vt6655/device_main.c
> index 83e4162..a3f5cd8 100644
> --- a/drivers/staging/vt6655/device_main.c
> +++ b/drivers/staging/vt6655/device_main.c
> @@ -1669,7 +1669,7 @@ static const struct ieee80211_ops vnt_mac_ops = {
> .reset_tsf = vnt_reset_tsf,
> };
>
> -int vnt_init(struct vnt_private *priv)
> +static int vnt_init(struct vnt_private *priv)
> {
> SET_IEEE80211_PERM_ADDR(priv->hw, priv->abyCurrentNetAddr);
>
> --
> 1.9.1
>
> --
> 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/
next prev parent reply other threads:[~2014-12-09 12:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-08 18:03 [PATCH 1/1] [PATCH] Staging:vt6655: sparse warning fix Adithya K
2014-12-09 12:34 ` Sudip Mukherjee [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-12-09 15:28 Adithya K
2015-01-13 3:39 ` Greg KH
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=20141209123425.GA5407@sudip-PC \
--to=sudipm.mukherjee@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=forest@alittletooquiet.net \
--cc=gclement@baobob.org \
--cc=gregkh@linuxfoundation.org \
--cc=guido@vanguardiasur.com.ar \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux.challenge1@gmail.com \
--cc=linux.challenge@gmail.com \
--cc=tvboxspy@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