All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: me@anmolsarma.in
Cc: devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/3] Staging: rtl8187se: ieee80211: ieee80211_softmac.c: mark symbols as static
Date: Thu, 9 Jan 2014 07:04:28 -0800	[thread overview]
Message-ID: <20140109150428.GA20411@kroah.com> (raw)
In-Reply-To: <9036792bea27cf00f564bbcb72f19de6b450f4a3.1389263965.git.me@anmolsarma.in>

On Thu, Jan 09, 2014 at 04:41:07PM +0530, me@anmolsarma.in wrote:
> From: Anmol Sarma <me@anmolsarma.in>
> 
> Fixes the following sparse warnings:
> 50:14: warning: symbol 'ieee80211_MFIE_rate_len' was not declared. Should it be
> static?
> 68:6: warning: symbol 'ieee80211_MFIE_Brate' was not declared. Should it be
> static?

Please don't line-wrap error messages like this, it makes it quite
messy, don't you think?


  reply	other threads:[~2014-01-09 15:04 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-09 11:11 [PATCH 0/3] Staging: rtl8187se: Sparse fixes me
2014-01-09 11:11 ` [PATCH 1/3] Staging: rtl8187se: r8180_core.c: mark symbols as static me
2014-01-09 11:11 ` [PATCH 2/3] Staging: rtl8187se: r8180_wx.c: " me
2014-01-09 11:11 ` [PATCH 3/3] Staging: rtl8187se: ieee80211: ieee80211_softmac.c: " me
2014-01-09 15:04   ` Greg KH [this message]
2014-01-09 15:15   ` Dan Carpenter
2014-01-09 19:44     ` [PATCH v2 0/3] Staging: rtl8187se: Sparse fixes Anmol Sarma
2014-01-09 19:44       ` [PATCH v2 1/3] Staging: rtl8187se: r8180_core.c: mark symbols as static Anmol Sarma
2014-01-09 19:44       ` [PATCH v2 2/3] Staging: rtl8187se: r8180_wx.c: make 'rtl8180_rates' static Anmol Sarma
2014-01-09 19:44       ` [PATCH v2 3/3] Staging: rtl8187se: ieee80211: ieee80211_softmac.c: mark symbols as static Anmol Sarma

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=20140109150428.GA20411@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=devel@driverdev.osuosl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=me@anmolsarma.in \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.