From: Nick <vincent@systemli.org>
To: Daniel Golle <daniel@makrotopia.org>
Cc: nbd@nbd.name, lorenzo.bianconi83@gmail.com,
ryder.lee@mediatek.com, kvalo@codeaurora.org,
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 v1] mt76: mt7615: mt7622: fix adhoc and ibss mode
Date: Fri, 8 Oct 2021 00:54:57 +0200 [thread overview]
Message-ID: <9de61dcc-cf6e-aeed-a077-756b697fb534@systemli.org> (raw)
In-Reply-To: <YV92Wjo+3dZ49DL6@makrotopia.org>
On 10/8/21 00:36, Daniel Golle wrote:
> On Thu, Oct 07, 2021 at 11:23:23PM +0200, Nick Hainke wrote:
>> Subject: [RFC v1] mt76: mt7615: mt7622: fix adhoc and ibss mode
> Ad-Hoc and IBSS mode are synonyms.
> What probably meant to write 'fix adhoc and mesh mode', right?
>
Yes. Or maybe even better "fix adhoc and meshpoint'. :)
I will update.
Bests
Nick
WARNING: multiple messages have this Message-ID (diff)
From: Nick <vincent@systemli.org>
To: Daniel Golle <daniel@makrotopia.org>
Cc: nbd@nbd.name, lorenzo.bianconi83@gmail.com,
ryder.lee@mediatek.com, kvalo@codeaurora.org,
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 v1] mt76: mt7615: mt7622: fix adhoc and ibss mode
Date: Fri, 8 Oct 2021 00:54:57 +0200 [thread overview]
Message-ID: <9de61dcc-cf6e-aeed-a077-756b697fb534@systemli.org> (raw)
In-Reply-To: <YV92Wjo+3dZ49DL6@makrotopia.org>
On 10/8/21 00:36, Daniel Golle wrote:
> On Thu, Oct 07, 2021 at 11:23:23PM +0200, Nick Hainke wrote:
>> Subject: [RFC v1] mt76: mt7615: mt7622: fix adhoc and ibss mode
> Ad-Hoc and IBSS mode are synonyms.
> What probably meant to write 'fix adhoc and mesh mode', right?
>
Yes. Or maybe even better "fix adhoc and meshpoint'. :)
I will update.
Bests
Nick
_______________________________________________
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: Nick <vincent@systemli.org>
To: Daniel Golle <daniel@makrotopia.org>
Cc: nbd@nbd.name, lorenzo.bianconi83@gmail.com,
ryder.lee@mediatek.com, kvalo@codeaurora.org,
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 v1] mt76: mt7615: mt7622: fix adhoc and ibss mode
Date: Fri, 8 Oct 2021 00:54:57 +0200 [thread overview]
Message-ID: <9de61dcc-cf6e-aeed-a077-756b697fb534@systemli.org> (raw)
In-Reply-To: <YV92Wjo+3dZ49DL6@makrotopia.org>
On 10/8/21 00:36, Daniel Golle wrote:
> On Thu, Oct 07, 2021 at 11:23:23PM +0200, Nick Hainke wrote:
>> Subject: [RFC v1] mt76: mt7615: mt7622: fix adhoc and ibss mode
> Ad-Hoc and IBSS mode are synonyms.
> What probably meant to write 'fix adhoc and mesh mode', right?
>
Yes. Or maybe even better "fix adhoc and meshpoint'. :)
I will update.
Bests
Nick
_______________________________________________
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-07 22:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-07 21:23 [RFC v1] mt76: mt7615: mt7622: fix adhoc and ibss mode Nick Hainke
2021-10-07 21:23 ` Nick Hainke
2021-10-07 21:23 ` Nick Hainke
2021-10-07 22:36 ` Daniel Golle
2021-10-07 22:36 ` Daniel Golle
2021-10-07 22:36 ` Daniel Golle
2021-10-07 22:54 ` Nick [this message]
2021-10-07 22:54 ` Nick
2021-10-07 22:54 ` Nick
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=9de61dcc-cf6e-aeed-a077-756b697fb534@systemli.org \
--to=vincent@systemli.org \
--cc=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 \
/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.