From: Kalle Valo <kvalo@codeaurora.org>
To: Allen Pais <apais@linux.microsoft.com>
Cc: Allen Pais <allen.lkml@gmail.com>,
ryder.lee@mediatek.com, netdev@vger.kernel.org,
linux-wireless@vger.kernel.org, ath11k@lists.infradead.org,
matthias.bgg@gmail.com, linux-mediatek@lists.infradead.org,
lorenzo.bianconi83@gmail.com, kuba@kernel.org,
davem@davemloft.net, nbd@nbd.name
Subject: Re: [PATCH v2 0/3] wireless: convert tasklets to use new
Date: Wed, 04 Nov 2020 18:38:56 +0200 [thread overview]
Message-ID: <87blgdqdpb.fsf@codeaurora.org> (raw)
In-Reply-To: <c3d71677-a428-f215-2ba8-4dd277a69fb6@linux.microsoft.com> (Allen Pais's message of "Tue, 3 Nov 2020 13:05:23 +0530")
Allen Pais <apais@linux.microsoft.com> writes:
>>
>> This series converts the remaining drivers to use new
>> tasklet_setup() API.
>>
>> The patches are based on wireless-drivers-next (c2568c8c9e63)
>
> Is this series queue? I haven't seen any email. This is the last
> series as part of the tasklet conversion effort.
They are queued in linux-wireless patchwork, see the link below. I have
lots of patches pending but hopefully I'll tackle most of them soon.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2020-11-04 16:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-07 10:33 [PATCH v2 0/3] wireless: convert tasklets to use new Allen Pais
2020-10-07 10:33 ` [PATCH v2 1/3] wireless: mt76: convert tasklets to use new tasklet_setup() API Allen Pais
2020-10-07 10:33 ` [PATCH v2 2/3] wireless: mt7601u: " Allen Pais
2020-11-07 11:29 ` Kalle Valo
2020-10-07 10:33 ` [PATCH v2 3/3] ath11k: " Allen Pais
2020-11-07 7:59 ` Kalle Valo
2020-11-03 7:35 ` [PATCH v2 0/3] wireless: convert tasklets to use new Allen Pais
2020-11-04 16:38 ` Kalle Valo [this message]
2020-11-05 3:33 ` Allen Pais
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=87blgdqdpb.fsf@codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=allen.lkml@gmail.com \
--cc=apais@linux.microsoft.com \
--cc=ath11k@lists.infradead.org \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=lorenzo.bianconi83@gmail.com \
--cc=matthias.bgg@gmail.com \
--cc=nbd@nbd.name \
--cc=netdev@vger.kernel.org \
--cc=ryder.lee@mediatek.com \
/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).