From: Sasha Levin <sashal@kernel.org>
To: Dietmar May <dmay@intellastar.com>
Cc: stable@vger.kernel.org, linux-wireless@vger.kernel.org
Subject: Re: wlcore update breaks on 4.9 and 4.4 kernel branches
Date: Sat, 5 Jan 2019 15:52:21 -0500 [thread overview]
Message-ID: <20190105205221.GB166797@sasha-vm> (raw)
In-Reply-To: <be76fc93-5bbc-9e00-3091-a57d13f2e485@intellastar.com>
On Thu, Jan 03, 2019 at 02:27:04PM -0500, Dietmar May wrote:
>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.
Thank you for the update!
--
Thanks,
Sasha
prev parent reply other threads:[~2019-01-05 20:52 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
2019-01-05 20:52 ` Sasha Levin [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=20190105205221.GB166797@sasha-vm \
--to=sashal@kernel.org \
--cc=dmay@intellastar.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).