All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stanislaw Gruszka <sgruszka@redhat.com>
To: wwguy <wey-yi.w.guy@intel.com>
Cc: "linville@tuxdriver.com" <linville@tuxdriver.com>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	"ipw3945-devel@lists.sourceforge.net"
	<ipw3945-devel@lists.sourceforge.net>
Subject: Re: [PATCH 1/1] iwl3945: iwl3945_good_plcp_health might not used
Date: Mon, 14 Feb 2011 10:06:49 +0100	[thread overview]
Message-ID: <20110214090620.GE2327@redhat.com> (raw)
In-Reply-To: <1297437769.20613.1300.camel@wwguy-ubuntu>

Hi Wey

On Fri, Feb 11, 2011 at 07:22:49AM -0800, wwguy wrote:
> On Fri, 2011-02-11 at 06:49 -0800, Stanislaw Gruszka wrote:
> > 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(-)
> > > 
> I see your point, but I also think it des not mean other driver doing
> bad, so we can do it too. do you agree?

Fully agree :-)

> I like to see the iwlwifi driver
> as clean as possible (do our best :-))
> hope it is ok for you.

Of course it is. But I do not complained about fixing warning, but about
posting it to -stable. Thats clearly not -stable fix as stated in
Documentation/stable_kernel_rules.txt .

I should have add that __maybe_unused to my patch, but I didn't.
What we could do now is fix warning in upstream and live with it
in -stable .

Stanislaw

  reply	other threads:[~2011-02-14  9:07 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
2011-02-11 15:22   ` wwguy
2011-02-14  9:06     ` Stanislaw Gruszka [this message]
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=20110214090620.GE2327@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.