From: Greg KH <greg@kroah.com>
To: Emmanuel Grumbach <emmanuel.grumbach@intel.com>
Cc: stable@vger.kernel.org, linux-wireless@vger.kernel.org
Subject: Re: [PATCH 3.16 0/7] Backort firmware monitor to 3.16
Date: Tue, 28 Oct 2014 14:22:31 +0800 [thread overview]
Message-ID: <20141028062231.GA12676@kroah.com> (raw)
In-Reply-To: <1414476686-3407-1-git-send-email-emmanuel.grumbach@intel.com>
On Tue, Oct 28, 2014 at 08:11:19AM +0200, Emmanuel Grumbach wrote:
> This patch series allows to use the firmware debugging features
> of iwlwifi on 3.16. These features are already in 3.17.
>
> I know that this patch series is not compliant with Greg's
> rules for stable patches. It is unlikely that these patches
> will be applied on vanilla 3.16 - I know that.
Good, because I just released the last 3.16-stable-rc kernel, so even if
I wanted to, I wouldn't take these :)
thanks,
greg k-h
next prev parent reply other threads:[~2014-10-28 6:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-28 6:11 [PATCH 3.16 0/7] Backort firmware monitor to 3.16 Emmanuel Grumbach
2014-10-28 6:11 ` [PATCH 3.16 1/7] iwlwifi: add device / firmware to fw-error-dump file Emmanuel Grumbach
2014-10-28 6:11 ` [PATCH 3.16 2/7] iwlwifi: rename iwl_mvm_fw_error_next_data Emmanuel Grumbach
2014-10-28 6:11 ` [PATCH 3.16 3/7] iwlwifi: pcie: add firmware monitor capabilities Emmanuel Grumbach
2014-10-28 6:11 ` [PATCH 3.16 4/7] iwlwifi: remove wrong comment about alignment in iwl-fw-error-dump.h Emmanuel Grumbach
2014-10-28 6:11 ` [PATCH 3.16 5/7] iwlwifi: mvm: don't collect logs in the interrupt thread Emmanuel Grumbach
2014-10-28 6:11 ` [PATCH 3.16 6/7] iwlwifi: mvm: kill iwl_mvm_fw_error_rxf_dump Emmanuel Grumbach
2014-10-28 6:11 ` [PATCH 3.16 7/7] iwlwifi: mvm: update layout of firmware error dump Emmanuel Grumbach
2014-10-28 6:22 ` Greg KH [this message]
2014-11-04 0:07 ` [PATCH 3.16 0/7] Backort firmware monitor to 3.16 Ben Hutchings
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=20141028062231.GA12676@kroah.com \
--to=greg@kroah.com \
--cc=emmanuel.grumbach@intel.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).