From: Sergey Matyukevich <sergey.matyukevich.os@quantenna.com>
To: Kalle Valo <kvalo@codeaurora.org>
Cc: linux-wireless@vger.kernel.org,
Igor Mitsyanko <igor.mitsyanko.os@quantenna.com>,
Avinash Patil <avinashp@quantenna.com>
Subject: Re: [v2,1/2] qtnfmac: lock access to h/w in tx path
Date: Thu, 21 Sep 2017 11:01:48 +0300 [thread overview]
Message-ID: <20170921080147.tvcztifyfwy2lp7g@bars> (raw)
In-Reply-To: <20170920123553.7121D6070F@smtp.codeaurora.org>
Hello Kalle,
> > Fix tx path regression. Lock should be held when queuing packets
> > to h/w fifos in order to properly handle configurations with
> > multiple enabled interfaces.
> >
> > Signed-off-by: Sergey Matyukevich <sergey.matyukevich.os@quantenna.com>
>
> 2 patches applied to wireless-drivers.git, thanks.
>
> 20da2ec06bfa qtnfmac: lock access to h/w in tx path
> a715b3a0efe7 qtnfmac: cancel scans on wireless interface changes
Could you please clarify a couple of points regarding wireless-drivers-next
and wireless-drivers trees. I checked development process article at
wireless.wiki.kernel.org, but it looks a bit outdated. So am I correct
assuming the following:
- these two fixes were applied to wireless-drivers because I asked to
to queue them to 4.14
- these two fixes will show up in wireless-drivers-next at some point
in the future after you move wireless-drivers-next forward, rebasing
it on top of one of the upcoming "-rc"
Regards,
Sergey
next prev parent reply other threads:[~2017-09-21 8:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-18 12:29 [PATCH v2 0/2] qtnfmac: misc fixes intended for 4.14 Sergey Matyukevich
2017-09-18 12:29 ` [PATCH v2 1/2] qtnfmac: lock access to h/w in tx path Sergey Matyukevich
2017-09-20 12:35 ` [v2,1/2] " Kalle Valo
2017-09-21 8:01 ` Sergey Matyukevich [this message]
2017-09-21 11:22 ` Kalle Valo
2017-09-21 11:56 ` Sergey Matyukevich
2017-09-18 12:29 ` [PATCH v2 2/2] qtnfmac: cancel scans on wireless interface changes Sergey Matyukevich
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=20170921080147.tvcztifyfwy2lp7g@bars \
--to=sergey.matyukevich.os@quantenna.com \
--cc=avinashp@quantenna.com \
--cc=igor.mitsyanko.os@quantenna.com \
--cc=kvalo@codeaurora.org \
--cc=linux-wireless@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).