linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Emmanuel Grumbach <egrumbach@gmail.com>
Cc: "stable@vger.kernel.org" <stable@vger.kernel.org>,
	linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: How to disable beacon filtering in iwlwifi in 3.13 and 3.14
Date: Mon, 19 May 2014 14:15:53 -0700	[thread overview]
Message-ID: <20140519211553.GA32321@kroah.com> (raw)
In-Reply-To: <537A685E.3040500@gmail.com>

On Mon, May 19, 2014 at 11:23:58PM +0300, Emmanuel Grumbach wrote:
> 
> 
> On 05/19/2014 10:41 PM, Greg KH wrote:
> > On Mon, May 19, 2014 at 01:40:34PM +0300, Emmanuel Grumbach wrote:
> >> Hi,
> >>
> >> I need to disable a feature on 3.13 and 3.14. But I don't have any
> >> patch upstream that I can point to as the patch that needs to be
> >> backported.
> >> We have a feature that is buggy in 3.13 and 3.14. We refactored (and
> >> fixed) this feature in 3.15 but the refactor is really not stable
> >> material, so basically, I can't backport the fix to 3.13 / 3.14. A
> >> user reported that disabling the feature solved (part of) his issues:
> >> https://bugzilla.kernel.org/show_bug.cgi?id=72601.
> >> OTOH, I don't have any patch in linux.git that could be backported to
> >> do what I want in 3.13 / 3.14 - i.e. disable the feature.
> >> What is the right process here? I understand that this isn't covered
> >> by the "stable rules". So what should I do here?
> > 
> > Get the maintainer's approval to apply this patch and I can queue it up.
> 
> Ok - thanks. It might be worthwhile to add this "exception path" in the Documentation :)

No, it's such a rare exception, I don't want to "encourage" anyone to
ever do it by documenting it.

thanks,

greg k-h

  reply	other threads:[~2014-05-19 21:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-19 10:40 How to disable beacon filtering in iwlwifi in 3.13 and 3.14 Emmanuel Grumbach
2014-05-19 19:41 ` Greg KH
2014-05-19 20:23   ` Emmanuel Grumbach
2014-05-19 21:15     ` Greg KH [this message]
2014-05-19 20:29   ` John W. Linville

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=20140519211553.GA32321@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=egrumbach@gmail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=stable@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;
as well as URLs for NNTP newsgroup(s).