From: Sasha Levin <sasha.levin@oracle.com>
To: "Grumbach, Emmanuel" <emmanuel.grumbach@intel.com>,
Greg KH <gregkh@linuxfoundation.org>
Cc: "stable@vger.kernel.org" <stable@vger.kernel.org>,
"gordan@bobich.net" <gordan@bobich.net>
Subject: Re: [PATCH v3.18] iwlwifi: pcie: support loading FW with extended mem range
Date: Thu, 10 Mar 2016 13:51:18 -0500 [thread overview]
Message-ID: <56E1C226.1040108@oracle.com> (raw)
In-Reply-To: <0BA3FCBA62E2DC44AF3030971E174FB32EA68A47@hasmsx107.ger.corp.intel.com>
On 03/10/2016 12:02 PM, Grumbach, Emmanuel wrote:
>
> On 03/10/2016 06:31 PM, Greg KH wrote:
>> > On Thu, Mar 10, 2016 at 10:46:22AM +0000, Grumbach, Emmanuel wrote:
>>> >> Hi Greg,
>>> >>
>>>>> >>>>
>>>>> >>>>
>>>>> >>>> On 02/07/2016 11:00 PM, Greg KH wrote:
>>>>>> >>>>> 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?
>>>>> >>>>
>>>>> >>>> That was fast :) 3.18 as said in the title of the patch. Do you have
>>>>> >>>> any preference on how to indicate that?
>>>> >>>
>>>> >>> Ugh, no, you did it right, I just didn't read the subject: my fault, sorry for the
>>>> >>> noise...
>>> >>
>>> >> Any reason this was not picked up for v3.18.28?
>>> >> Do I miss anything?
>> >
>> > Why are you asking me about 3.18-stable?
>> >
>> > confused,
>> >
> Ouch - somehow, I was convinced that you maintain all the stable
> kernels, at least all those being listed in kernel.org. Sorry...
Sorry about that, my scripts skipped it because it didn't have a cc: stable@ tag. Fixed that and added it to the queue.
Thanks,
Sasha
next prev parent reply other threads:[~2016-03-10 18:51 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
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 [this message]
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=56E1C226.1040108@oracle.com \
--to=sasha.levin@oracle.com \
--cc=emmanuel.grumbach@intel.com \
--cc=gordan@bobich.net \
--cc=gregkh@linuxfoundation.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).