From: Kalle Valo <kvalo@codeaurora.org>
To: Stanislaw Gruszka <sgruszka@redhat.com>
Cc: Lorenzo Bianconi <lorenzo.bianconi@redhat.com>,
nbd@nbd.name, linux-wireless@vger.kernel.org
Subject: Re: [PATCH v2 00/19] add mt76x2u support to mt76 driver
Date: Tue, 31 Jul 2018 13:33:55 +0300 [thread overview]
Message-ID: <87ftzzae3w.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <20180731102714.GD5009@redhat.com> (Stanislaw Gruszka's message of "Tue, 31 Jul 2018 12:27:15 +0200")
Stanislaw Gruszka <sgruszka@redhat.com> writes:
> On Tue, Jul 31, 2018 at 12:54:32PM +0300, Kalle Valo wrote:
>> Lorenzo Bianconi <lorenzo.bianconi@redhat.com> writes:
>>
>> > Add usb layer to mt76 driver in order to support mt76x2u based devices.
>> > Move common code between pci and usb in mt76x2-common module in order to
>> > remove pci dependency from usb driver
>> >
>> > Changes since v1:
>> > - rebase on top of wireless-drivers-next master branch
>> > - fix mt7662u fw definitions
>> > - remove unused len variable in mt76x2u_remove_dma_hdr()
>> > - move mt76u_mcu_fw_reset routine in mt76-usb module in order
>> > to be reused by mt76x0 driver
>> > - move mt76u_mcu_init_rx routine in mt76-usb module in order
>> > to be reused by mt76x0 driver
>>
>> My deadline for 4.19 is most likely this Friday (if the merge window
>> starts on Sunday) so I would need to apply these tomorrow by latest to
>> have some time in linux-next. Are everyone happy with this set?
>
> I'm ok with this set.
>
> If I'll post mt76x0 v3 would you take it in this cycle or should
> I rather wait for next one ?
I applied Lorenzo's patchset to pending branch in wireless-drivers-next.
If you can use that as the baseline and submit your patchset by tomorrow
morning I can try to get it to v4.19. But I'm not promising anything :)
--
Kalle Valo
prev parent reply other threads:[~2018-07-31 12:13 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-31 8:09 [PATCH v2 00/19] add mt76x2u support to mt76 driver Lorenzo Bianconi
2018-07-31 8:09 ` [PATCH v2 01/19] mt76: move MT_TXD_INFO, MT_MCU_MSG and MT_RX_FCE_INFO defs in dma.h Lorenzo Bianconi
2018-08-02 18:49 ` Kalle Valo
2018-07-31 8:09 ` [PATCH v2 02/19] mt76x2: move mt76x2_fw_header and mt76x2_patch_header definitions in mcu.h Lorenzo Bianconi
2018-07-31 8:09 ` [PATCH v2 03/19] mt76x2: move utility routines in mt76x2.h Lorenzo Bianconi
2018-07-31 8:09 ` [PATCH v2 04/19] mt76x2: introduce mt76x2_init_device routine Lorenzo Bianconi
2018-07-31 8:09 ` [PATCH v2 05/19] mt76x2: move interface_modes definition in mt76x2_init Lorenzo Bianconi
2018-07-31 8:09 ` [PATCH v2 06/19] mt76x2: introduce mt76x2_mac_load_tx_status routine Lorenzo Bianconi
2018-07-31 8:09 ` [PATCH v2 07/19] mt76x2: add napi struct to mt76_rx_poll_complete/mt76_rx_complete signatures Lorenzo Bianconi
2018-07-31 8:09 ` [PATCH v2 08/19] mt76x2: add buffer len to mt76x2_mac_write_txwi signature Lorenzo Bianconi
2018-07-31 8:09 ` [PATCH v2 09/19] mt76: rename mt76_tx_queue_skb in mt76_dma_tx_queue_skb Lorenzo Bianconi
2018-07-31 8:09 ` [PATCH v2 10/19] mt76: introduce tx_queue_skb function pointer in mt76_bus_ops Lorenzo Bianconi
2018-07-31 8:09 ` [PATCH v2 11/19] mt76: introduce mt76x2-common module Lorenzo Bianconi
2018-07-31 8:09 ` [PATCH v2 12/19] mt76: add mt76x2_tx_common to " Lorenzo Bianconi
2018-07-31 8:09 ` [PATCH v2 13/19] mt76: add mt76x2_mac_common " Lorenzo Bianconi
2018-07-31 8:09 ` [PATCH v2 14/19] mt76: add mt76x2_init_common " Lorenzo Bianconi
2018-07-31 8:09 ` [PATCH v2 15/19] mt76: add mt76x2_common " Lorenzo Bianconi
2018-07-31 8:09 ` [PATCH v2 16/19] mt76: add mt76x2_phy_common " Lorenzo Bianconi
2018-07-31 8:09 ` [PATCH v2 17/19] mt76: move mt76x2_debugfs in mt76-common module Lorenzo Bianconi
2018-07-31 8:09 ` [PATCH v2 18/19] mt76: add usb support to mt76 layer Lorenzo Bianconi
2018-07-31 8:09 ` [PATCH v2 19/19] mt76: add driver code for MT76x2u based devices Lorenzo Bianconi
2018-07-31 9:54 ` [PATCH v2 00/19] add mt76x2u support to mt76 driver Kalle Valo
2018-07-31 10:27 ` Stanislaw Gruszka
2018-07-31 10:33 ` Kalle Valo [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=87ftzzae3w.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@codeaurora.org \
--cc=linux-wireless@vger.kernel.org \
--cc=lorenzo.bianconi@redhat.com \
--cc=nbd@nbd.name \
--cc=sgruszka@redhat.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).