From: Dietmar May <dmay@intellastar.com>
To: Sasha Levin <sashal@kernel.org>
Cc: stable@vger.kernel.org, linux-wireless@vger.kernel.org
Subject: Re: wlcore update breaks on 4.9 and 4.4 kernel branches
Date: Thu, 3 Jan 2019 14:27:04 -0500 [thread overview]
Message-ID: <be76fc93-5bbc-9e00-3091-a57d13f2e485@intellastar.com> (raw)
In-Reply-To: <20181212064051.GA2746@sasha-vm>
Sasha,
I've just confirmed that this problem is no longer present in 4.4.169
either, as expected.
Sorry for the delay - we're on 4.9, so the 4.4 branch doesn't impact us.
Just wanted to let you know so you have full closure on this issue.
Dietmar
------------------------------------------------------------------------
On 12/12/18 1:40 AM, Sasha Levin wrote:
> On Tue, Dec 11, 2018 at 03:29:31PM -0500, Dietmar May wrote:
>> Sasha,
>>
>> I've verified that 4.9.143 no longer exhibits this problem.
>
> Thanks for confirming!
>
>> The revert hasn't shown up in 4.4 yet; but I'll verify once merged
>> there.
>
> There was no 4.4 release yet; it's coming, I promise :)
>
> --
> Thanks,
> Sasha
--
This email and any information disclosed in connection herewith, whether
written or oral, is the property of Intellastar LLC, and is intended only
for the person or entity to which it is addressed. This email may contain
information that is privileged confidential or otherwise protected from
disclosure. Distributing or copying any information contained in this email
to anyone other than the intended recipient is strictly prohibited.
next prev parent reply other threads:[~2019-01-03 19:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-29 22:56 wlcore update breaks on 4.9 and 4.4 kernel branches Dietmar May
2018-12-02 15:08 ` Sasha Levin
2018-12-11 20:34 ` Dietmar May
[not found] ` <72dcddb8-a44a-d50c-bae6-c51180e53cc8@intellastar.com>
2018-12-12 6:40 ` Sasha Levin
2019-01-03 19:27 ` Dietmar May [this message]
2019-01-05 20:52 ` 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=be76fc93-5bbc-9e00-3091-a57d13f2e485@intellastar.com \
--to=dmay@intellastar.com \
--cc=linux-wireless@vger.kernel.org \
--cc=sashal@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).