From: Nick <vincent@systemli.org>
To: Daniel Golle <daniel@makrotopia.org>,
Frank Wunderlich <frank-w@public-files.de>
Cc: Kalle Valo <kvalo@codeaurora.org>,
nbd@nbd.name, lorenzo.bianconi83@gmail.com,
ryder.lee@mediatek.com, davem@davemloft.net, kuba@kernel.org,
matthias.bgg@gmail.com, sean.wang@mediatek.com,
shayne.chen@mediatek.com, linux-wireless@vger.kernel.org,
netdev@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, linux-kernel@vger.kernel.org,
Robert Foss <robert.foss@linaro.org>
Subject: Re: [RFC v2] mt76: mt7615: mt7622: fix ibss and meshpoint
Date: Mon, 18 Oct 2021 12:13:19 +0200 [thread overview]
Message-ID: <f2a5f060-3c25-d22a-3ff5-7c42609df2df@systemli.org> (raw)
In-Reply-To: <716d8b51-5a4e-e074-aa1a-4d2055cf18cf@systemli.org>
Sorry, I should have added, that the simultanously mode was not working
on the mt7622 with and without patch. With mt7615e it was working.
Bests
Nick
On 10/18/21 12:11, Nick wrote:
> On 10/17/21 15:52, Daniel Golle wrote:
>
>> Independently of each other or simultanously?
>
> My tests were done simultanously. The "plus" means to the same time
> with my post. However, simultanously AP and AdHoc was never be
> possible with the patch, nor without the patch.
>
> Bests
> Nick
>
next prev parent reply other threads:[~2021-10-18 10:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-07 22:57 [RFC v2] mt76: mt7615: mt7622: fix ibss and meshpoint Nick Hainke
2021-10-09 8:32 ` Kalle Valo
2021-10-09 10:37 ` Nick
2021-10-09 13:22 ` Daniel Golle
2021-10-11 9:12 ` Nick
2021-10-17 12:28 ` Aw: " Frank Wunderlich
2021-10-17 13:52 ` Daniel Golle
2021-10-18 10:11 ` Nick
2021-10-18 10:13 ` Nick [this message]
2021-10-18 10:16 ` Felix Fietkau
2021-10-19 7:19 ` Kalle Valo
2021-10-23 7:30 ` [RFC,v2] " Kalle Valo
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=f2a5f060-3c25-d22a-3ff5-7c42609df2df@systemli.org \
--to=vincent@systemli.org \
--cc=daniel@makrotopia.org \
--cc=davem@davemloft.net \
--cc=frank-w@public-files.de \
--cc=kuba@kernel.org \
--cc=kvalo@codeaurora.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.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=robert.foss@linaro.org \
--cc=ryder.lee@mediatek.com \
--cc=sean.wang@mediatek.com \
--cc=shayne.chen@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).