From: Kalle Valo <kvalo@codeaurora.org>
To: Luca Coelho <luca@coelho.fi>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
torvalds@linux-foundation.org, "Grumbach\,
Emmanuel" <emmanuel.grumbach@intel.com>,
linuxwifi <linuxwifi@intel.com>
Subject: Re: pull-request: iwlwifi 2016-07-11
Date: Wed, 13 Jul 2016 10:54:41 +0300 [thread overview]
Message-ID: <87mvlmynum.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <1468233921.25088.107.camel@coelho.fi> (Luca Coelho's message of "Mon, 11 Jul 2016 13:45:21 +0300")
Luca Coelho <luca@coelho.fi> writes:
> This is a fix for a warning that was spotted by Linus. We already have
> this patch queued in -next, but it should have gone to -fixes. I hope
> it is still possible to send it for 4.7. And it shouldn't be a problem
> to have it in both, right? I guess git merge would take care of that.
Like we discussed privately, even if iwlwifi was printing warnings the
connection was still working for Linus so this is not critical enough
for 4.7 so late in the cycle. So let's drop this and the fix can go to
4.8 as planned.
--
Kalle Valo
prev parent reply other threads:[~2016-07-13 7:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-11 10:45 pull-request: iwlwifi 2016-07-11 Luca Coelho
2016-07-13 7:54 ` Kalle Valo [this message]
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=87mvlmynum.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@codeaurora.org \
--cc=emmanuel.grumbach@intel.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linuxwifi@intel.com \
--cc=luca@coelho.fi \
--cc=torvalds@linux-foundation.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).