All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Emmanuel Grumbach <egrumbach@gmail.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
	Emmanuel Grumbach <emmanuel.grumbach@intel.com>,
	"stable@vger.kernel.org" <stable@vger.kernel.org>,
	linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH 3.10 0/3] Enable 7000 device family on 3.10
Date: Tue, 20 Aug 2013 14:25:24 -0700	[thread overview]
Message-ID: <20130820212524.GA9902@kroah.com> (raw)
In-Reply-To: <CANUX_P0BxGr9coDjOmHJm+8kVJVsM9XiTDTVsb_kysuRmcmpNw@mail.gmail.com>

On Tue, Aug 20, 2013 at 11:22:21PM +0300, Emmanuel Grumbach wrote:
> On Tue, Aug 6, 2013 at 4:42 PM, Greg KH <greg@kroah.com> wrote:
> > On Tue, Aug 06, 2013 at 02:39:39PM +0200, Johannes Berg wrote:
> >> [Emmanuel is on vacation, I'll cover for him]
> >>
> >> On Fri, 2013-08-02 at 17:02 +0800, Greg KH wrote:
> >> > On Mon, Jul 15, 2013 at 02:44:57PM +0300, Emmanuel Grumbach wrote:
> >> > > This small patch series enables 7260 and 3160 devices on 3.10
> >> > > kernel. Three patches are already in linux.git (3.11-rc1).
> >> > > One patch is 3.10 specific and disables configuration that is not
> >> > > supported in 3.10.
> >> >
> >> > I need the git commit id of these patches in Linus's tree before I can
> >> > apply them.  Please resend them with that information.
> >>
> >> The second and third patch does have it, and the first patch is only
> >> relevant for 3.10 since 3.11 will have more device types enabled, we
> >> just didn't get all the code in. This seems to be described in the
> >> commit log, do you want more details?
> >
> > Yes, please resend them with those details.  For me to take a patch that
> > is not in Linus's tree is a big deal, I need a whole lot of
> > justification for it.
> >
> 
> Just got back. Sorry for the delay.
> I guess I will just drop that patch that is not in Linus's tree.
> This patch disables a feature that is not likely to be used but we
> *know* it is buggy.
> So people who want more than just associating to their router will see
> a bug in 3.10.
> I guess we can leave with that since I was suggesting to disable the
> feature anyway.

Why would this patch not go to Linus's tree?  If it's broken, fix it,
and I can take the backported patch into the 3.10 tree.

> So - do you want to resend, or you can apply the 2 patches I sent as is?

Please resend.

thanks,

greg k-h

  reply	other threads:[~2013-08-20 21:25 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-15 11:44 [PATCH 3.10 0/3] Enable 7000 device family on 3.10 Emmanuel Grumbach
2013-07-15 11:44 ` [PATCH 3.10 1/3] iwlwifi: mvm: support BSS only Emmanuel Grumbach
2013-07-15 11:44 ` [PATCH 3.10 2/3] iwlwifi: mvm: adjust firmware D3 configuration API Emmanuel Grumbach
2013-07-15 11:45 ` [PATCH 3.10 3/3] iwlwifi: bump required firmware API version for 3160/7260 Emmanuel Grumbach
2013-08-02  9:02 ` [PATCH 3.10 0/3] Enable 7000 device family on 3.10 Greg KH
2013-08-06 12:39   ` Johannes Berg
2013-08-06 13:42     ` Greg KH
2013-08-20 20:22       ` Emmanuel Grumbach
2013-08-20 21:25         ` Greg KH [this message]
2013-08-21  5:46           ` Grumbach, Emmanuel
  -- strict thread matches above, loose matches on Subject: below --
2013-07-15 11:24 Emmanuel Grumbach
2013-07-15 11:19 Emmanuel Grumbach

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=20130820212524.GA9902@kroah.com \
    --to=greg@kroah.com \
    --cc=egrumbach@gmail.com \
    --cc=emmanuel.grumbach@intel.com \
    --cc=johannes@sipsolutions.net \
    --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 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.