All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Emmanuel Grumbach <emmanuel.grumbach@intel.com>
Cc: stable@vger.kernel.org, Arik Nemtsov <arik@wizery.com>,
	Arik Nemtsov <arikx.nemtsov@intel.com>
Subject: Re: [PATCH v3.18] iwlwifi: pcie: support loading FW with extended mem range
Date: Sun, 7 Feb 2016 13:00:18 -0800	[thread overview]
Message-ID: <20160207210018.GA20507@kroah.com> (raw)
In-Reply-To: <1454878268-12184-1-git-send-email-emmanuel.grumbach@intel.com>

On Sun, Feb 07, 2016 at 10:51:08PM +0200, Emmanuel Grumbach wrote:
> From: Arik Nemtsov <arik@wizery.com>
> 
> [commit fe45773b5baa154468416aac1304f6325939f775 upstream]
> 
> Toggle the LMPM_CHICK register when writing chunks into the FW's extended
> SRAM. This tells the FW to put the chunk into a different memory space.
> 
> Signed-off-by: Arik Nemtsov <arikx.nemtsov@intel.com>
> Signed-off-by: Emmanuel Grumbach <emmanuel.grumbach@intel.com>
> ---
> backporting this patch to 3.18 fixes
> https://bugzilla.kernel.org/show_bug.cgi?id=109531
> ---
>  drivers/net/wireless/iwlwifi/iwl-prph.h   |  6 ++++++
>  drivers/net/wireless/iwlwifi/pcie/trans.c | 26 ++++++++++++++++++++++----
>  2 files changed, 28 insertions(+), 4 deletions(-)

What stable tree(s) do you want this to be applied to?

thanks,

greg k-h

  reply	other threads:[~2016-02-07 21:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-07 20:51 [PATCH v3.18] iwlwifi: pcie: support loading FW with extended mem range Emmanuel Grumbach
2016-02-07 21:00 ` Greg KH [this message]
2016-02-07 21:02   ` Grumbach, Emmanuel
2016-02-07 21:19     ` Greg KH
2016-03-10 10:46       ` Grumbach, Emmanuel
2016-03-10 16:30         ` Greg KH
2016-03-10 17:02           ` Grumbach, Emmanuel
2016-03-10 18:51             ` Sasha Levin
2016-03-10 19:18               ` Grumbach, Emmanuel
2016-03-10 19:34                 ` Sasha Levin

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=20160207210018.GA20507@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=arik@wizery.com \
    --cc=arikx.nemtsov@intel.com \
    --cc=emmanuel.grumbach@intel.com \
    --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.