From: Daniel Golle <daniel@makrotopia.org>
To: Nick <vincent@systemli.org>
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: Sat, 9 Oct 2021 14:22:16 +0100 [thread overview]
Message-ID: <YWGXiExg1uBIFr2c@makrotopia.org> (raw)
In-Reply-To: <274013cd-29e4-9202-423b-bd2b2222d6b8@systemli.org>
On Sat, Oct 09, 2021 at 12:37:53PM +0200, Nick wrote:
> On 10/9/21 10:32, Kalle Valo wrote:
>
> > Nick Hainke <vincent@systemli.org> writes:
> >
> > > Fixes: d8d59f66d136 ("mt76: mt7615: support 16 interfaces").
> > The fixes tag should be in the end, before Signed-off-by tags. But I can
> > fix that during commit.
> Thanks for feedback. Already changed that locally but I did not want to spam
> you with another RFC v3. :)
> I was able to organize me a BPI-MT7615 PCIE Express Card. With and without
> this patch beacons were sent on the mt7615 pcie, so the patch did not make
> any difference. However, the mt7622 wifi will only work with my patch.
Does Mesh+AP or Ad-Hoc+AP also work on MT7622 and does it still work on
MT7615E card with your patch applied?
_______________________________________________
Linux-mediatek mailing list
Linux-mediatek@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-mediatek
WARNING: multiple messages have this Message-ID (diff)
From: Daniel Golle <daniel@makrotopia.org>
To: Nick <vincent@systemli.org>
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: Sat, 9 Oct 2021 14:22:16 +0100 [thread overview]
Message-ID: <YWGXiExg1uBIFr2c@makrotopia.org> (raw)
In-Reply-To: <274013cd-29e4-9202-423b-bd2b2222d6b8@systemli.org>
On Sat, Oct 09, 2021 at 12:37:53PM +0200, Nick wrote:
> On 10/9/21 10:32, Kalle Valo wrote:
>
> > Nick Hainke <vincent@systemli.org> writes:
> >
> > > Fixes: d8d59f66d136 ("mt76: mt7615: support 16 interfaces").
> > The fixes tag should be in the end, before Signed-off-by tags. But I can
> > fix that during commit.
> Thanks for feedback. Already changed that locally but I did not want to spam
> you with another RFC v3. :)
> I was able to organize me a BPI-MT7615 PCIE Express Card. With and without
> this patch beacons were sent on the mt7615 pcie, so the patch did not make
> any difference. However, the mt7622 wifi will only work with my patch.
Does Mesh+AP or Ad-Hoc+AP also work on MT7622 and does it still work on
MT7615E card with your patch applied?
WARNING: multiple messages have this Message-ID (diff)
From: Daniel Golle <daniel@makrotopia.org>
To: Nick <vincent@systemli.org>
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: Sat, 9 Oct 2021 14:22:16 +0100 [thread overview]
Message-ID: <YWGXiExg1uBIFr2c@makrotopia.org> (raw)
In-Reply-To: <274013cd-29e4-9202-423b-bd2b2222d6b8@systemli.org>
On Sat, Oct 09, 2021 at 12:37:53PM +0200, Nick wrote:
> On 10/9/21 10:32, Kalle Valo wrote:
>
> > Nick Hainke <vincent@systemli.org> writes:
> >
> > > Fixes: d8d59f66d136 ("mt76: mt7615: support 16 interfaces").
> > The fixes tag should be in the end, before Signed-off-by tags. But I can
> > fix that during commit.
> Thanks for feedback. Already changed that locally but I did not want to spam
> you with another RFC v3. :)
> I was able to organize me a BPI-MT7615 PCIE Express Card. With and without
> this patch beacons were sent on the mt7615 pcie, so the patch did not make
> any difference. However, the mt7622 wifi will only work with my patch.
Does Mesh+AP or Ad-Hoc+AP also work on MT7622 and does it still work on
MT7615E card with your patch applied?
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-10-09 13:23 UTC|newest]
Thread overview: 33+ 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-07 22:57 ` Nick Hainke
2021-10-07 22:57 ` Nick Hainke
2021-10-09 8:32 ` Kalle Valo
2021-10-09 8:32 ` Kalle Valo
2021-10-09 10:37 ` Nick
2021-10-09 10:37 ` Nick
2021-10-09 10:37 ` Nick
2021-10-09 13:22 ` Daniel Golle [this message]
2021-10-09 13:22 ` Daniel Golle
2021-10-09 13:22 ` Daniel Golle
2021-10-11 9:12 ` Nick
2021-10-11 9:12 ` Nick
2021-10-11 9:12 ` Nick
2021-10-17 12:28 ` Aw: " Frank Wunderlich
2021-10-17 12:28 ` Frank Wunderlich
2021-10-17 12:28 ` Frank Wunderlich
2021-10-17 13:52 ` Daniel Golle
2021-10-17 13:52 ` Daniel Golle
2021-10-17 13:52 ` Daniel Golle
2021-10-18 10:11 ` Nick
2021-10-18 10:11 ` Nick
2021-10-18 10:11 ` Nick
2021-10-18 10:13 ` Nick
2021-10-18 10:13 ` Nick
2021-10-18 10:13 ` Nick
2021-10-18 10:16 ` Felix Fietkau
2021-10-18 10:16 ` Felix Fietkau
2021-10-18 10:16 ` Felix Fietkau
2021-10-19 7:19 ` Kalle Valo
2021-10-19 7:19 ` Kalle Valo
2021-10-23 7:30 ` [RFC,v2] " Kalle Valo
2021-10-23 7:30 ` 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=YWGXiExg1uBIFr2c@makrotopia.org \
--to=daniel@makrotopia.org \
--cc=davem@davemloft.net \
--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 \
--cc=vincent@systemli.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.