From: Stanislaw Gruszka <sgruszka@redhat.com>
To: Wey-Yi Guy <wey-yi.w.guy@intel.com>
Cc: linville@tuxdriver.com, linux-wireless@vger.kernel.org,
ipw3945-devel@lists.sourceforge.net
Subject: Re: [PATCH 1/1] iwl3945: iwl3945_good_plcp_health might not used
Date: Fri, 11 Feb 2011 15:49:52 +0100 [thread overview]
Message-ID: <20110211144951.GA2278@redhat.com> (raw)
In-Reply-To: <1297354593-22897-1-git-send-email-wey-yi.w.guy@intel.com>
On Thu, Feb 10, 2011 at 08:16:33AM -0800, Wey-Yi Guy wrote:
> remove plcp check for 3945, mark the function __maybe_unused
>
> Signed-off-by: Wey-Yi Guy <wey-yi.w.guy@intel.com>
> Cc: <stable@kernel.org> # .35+: c91d015: iwl3945: remove plcp check
> Cc: stable@kernel.org # 2.6.35+
> ---
> drivers/net/wireless/iwlwifi/iwl-3945.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/drivers/net/wireless/iwlwifi/iwl-3945.c b/drivers/net/wireless/iwlwifi/iwl-3945.c
> index 3eb14fd..eb82341 100644
> --- a/drivers/net/wireless/iwlwifi/iwl-3945.c
> +++ b/drivers/net/wireless/iwlwifi/iwl-3945.c
> @@ -408,7 +408,7 @@ static void iwl3945_accumulative_statistics(struct iwl_priv *priv,
> * When the plcp error is exceeding the thresholds, reset the radio
> * to improve the throughput.
> */
> -static bool iwl3945_good_plcp_health(struct iwl_priv *priv,
> +static bool __maybe_unused iwl3945_good_plcp_health(struct iwl_priv *priv,
> struct iwl_rx_packet *pkt)
> {
> bool rc = true;
I was aware about that warning, but did not fix it, because when I compile
kernel, I can see lot's of other warnings and I have plan to clean
that iwl3945 code.
Does it something that really need to be fixed in -stable? I mean
should we bother stable maintainers about that?
Stanislaw
next prev parent reply other threads:[~2011-02-11 14:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-10 16:16 [PATCH 1/1] iwl3945: iwl3945_good_plcp_health might not used Wey-Yi Guy
2011-02-11 14:49 ` Stanislaw Gruszka [this message]
2011-02-11 15:22 ` wwguy
2011-02-14 9:06 ` Stanislaw Gruszka
2011-02-14 15:27 ` wwguy
2011-02-14 9:55 ` Johannes Berg
2011-02-14 15:25 ` wwguy
2011-02-14 15:28 ` Johannes Berg
2011-02-14 15:48 ` wwguy
2011-02-14 15:54 ` Johannes Berg
2011-02-14 15:57 ` wwguy
2011-02-14 20:10 ` John W. Linville
2011-02-14 20:31 ` wwguy
2011-02-14 21:05 ` John W. Linville
2011-02-14 21:28 ` David Miller
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=20110211144951.GA2278@redhat.com \
--to=sgruszka@redhat.com \
--cc=ipw3945-devel@lists.sourceforge.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=wey-yi.w.guy@intel.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 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.