From: Stanislaw Gruszka <sgruszka-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Sid Hayn <sidhayn-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: Matthias Brugger
<matthias.bgg-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
Lorenzo Bianconi
<lorenzo.bianconi-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
linux-mediatek-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
linux-wireless
<linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Felix Fietkau <nbd-Vt+b4OUoWG0@public.gmane.org>
Subject: Re: mt76x[02]u 802.11w support
Date: Mon, 17 Dec 2018 16:46:30 +0100 [thread overview]
Message-ID: <20181217154628.GA4773@redhat.com> (raw)
In-Reply-To: <CAM0KTbBV_YZqt6kkrKeY5tRtKn10UOLQY3EyTKPY+zLzht7sgg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On Mon, Dec 17, 2018 at 10:07:43AM -0500, Sid Hayn wrote:
> Interestingly when I asked for the monitor mode patch to be ported it
> was initially refused and then just kind of happened a few weeks
> later.
It was not quite like that. It was refused to apply on 4.19-rcX due to
-next merge -rc conflict that it will cause. And it was promised
that fixes will be backported thought -stable.
Regarding this case, there is no single commit that add 802.11w support
we could request to add to -stable. It was added together with other
features in:
commit 0ae976a11b4fb5704b597e103b5189237641c1a1
Author: Lorenzo Bianconi <lorenzo.bianconi-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Date: Thu Sep 6 11:18:41 2018 +0200
mt76x0: init hw capabilities
which depend on switching mt76x0u to mt76-usb layer.
So I'm not sure how this request should be satisfied.
Regards
Stanislaw
next prev parent reply other threads:[~2018-12-17 15:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-13 14:26 mt76x[02]u 802.11w support Sid Hayn
[not found] ` <CAM0KTbBUXJsBfO0=hQgeTGVteym6iuObdyNynWumQnnGY0L3wg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2018-12-13 14:39 ` Lorenzo Bianconi
[not found] ` <20181213143947.GA11947-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2018-12-15 3:43 ` Sid Hayn
2018-12-16 10:39 ` Matthias Brugger
[not found] ` <dd275289-99d0-54a8-9ac5-cb137123950a-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2018-12-17 15:07 ` Sid Hayn
[not found] ` <CAM0KTbBV_YZqt6kkrKeY5tRtKn10UOLQY3EyTKPY+zLzht7sgg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2018-12-17 15:46 ` Stanislaw Gruszka [this message]
[not found] ` <20181217154628.GA4773-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2018-12-18 8:09 ` Stanislaw Gruszka
[not found] ` <20181218080939.GA16795-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2018-12-18 18:38 ` Sid Hayn
[not found] ` <CAM0KTbCWtwYE3DzmqeHSs3m7A7JojeFFs2_Mp1q5Kg=ySaN0Rw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2018-12-19 7:47 ` Stanislaw Gruszka
[not found] ` <20181219074743.GA3538-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2018-12-19 17:08 ` Sid Hayn
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=20181217154628.GA4773@redhat.com \
--to=sgruszka-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
--cc=linux-mediatek-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=lorenzo.bianconi-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=matthias.bgg-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=nbd-Vt+b4OUoWG0@public.gmane.org \
--cc=sidhayn-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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).