From: Johannes Berg <johannes@sipsolutions.net>
To: Stanislaw Gruszka <stf_xl@wp.pl>, Rosen Penev <rosenp@gmail.com>
Cc: linux-wireless@vger.kernel.org, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
Matthias Brugger <matthias.bgg@gmail.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
"open list:MIPS" <linux-mips@vger.kernel.org>,
"moderated list:ARM/Mediatek SoC support"
<linux-arm-kernel@lists.infradead.org>,
"moderated list:ARM/Mediatek SoC support"
<linux-mediatek@lists.infradead.org>
Subject: Re: [PATCHv3 wireless-next 3/7] wifi: rt2800soc: allow loading from OF
Date: Sun, 13 Jul 2025 10:49:54 +0200 [thread overview]
Message-ID: <36c4cd5f263e4bae22a1779a9befd24dacd5d3bf.camel@sipsolutions.net> (raw)
In-Reply-To: <20250713071532.GA18469@wp.pl>
On Sun, 2025-07-13 at 09:15 +0200, Stanislaw Gruszka wrote:
>
> Can be done as separate patch since you already
> posed v4.
Maybe I should point out that I've simply been dropping the patches
unseen because they don't even apply.
johannes
next prev parent reply other threads:[~2025-07-13 8:50 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-10 20:08 [PATCHv3 wireless-next 0/7] wifi: rt2x00: add OF bindings + cleanup Rosen Penev
2025-07-10 20:08 ` [PATCHv3 wireless-next 1/7] wifi: rt2x00: add COMPILE_TEST Rosen Penev
2025-07-12 8:59 ` Stanislaw Gruszka
2025-07-10 20:08 ` [PATCHv3 wireless-next 2/7] wifi: rt2x00: remove mod_name from platform_driver Rosen Penev
2025-07-12 8:59 ` Stanislaw Gruszka
2025-07-10 20:08 ` [PATCHv3 wireless-next 3/7] wifi: rt2800soc: allow loading from OF Rosen Penev
2025-07-12 10:14 ` Stanislaw Gruszka
2025-07-12 19:02 ` Rosen Penev
2025-07-13 7:15 ` Stanislaw Gruszka
2025-07-13 8:49 ` Johannes Berg [this message]
2025-07-13 11:06 ` Johannes Berg
2025-07-10 20:08 ` [PATCHv3 wireless-next 4/7] wifi: rt2800: move 2x00soc to 2800soc Rosen Penev
2025-07-12 10:20 ` Stanislaw Gruszka
2025-07-10 20:08 ` [PATCHv3 wireless-next 5/7] wifi: rt2x00: soc: modernize probe Rosen Penev
2025-07-11 14:01 ` Alexander Savchenko
2025-07-11 20:33 ` Rosen Penev
2025-07-10 20:08 ` [PATCHv3 wireless-next 6/7] MIPS: dts: ralink: mt7620a: add wifi Rosen Penev
2025-07-10 20:08 ` [PATCHv3 wireless-next 7/7] dt-bindings: net: wireless: rt2800: add Rosen Penev
2025-07-10 21:39 ` Krzysztof Kozlowski
2025-07-10 22:40 ` Rosen Penev
2025-07-11 7:48 ` Krzysztof Kozlowski
2025-07-12 10:40 ` Stanislaw Gruszka
2025-07-12 16:53 ` Krzysztof Kozlowski
2025-07-12 16:59 ` Krzysztof Kozlowski
2025-07-12 23:20 ` Julian Calaby
2025-07-13 8:53 ` Krzysztof Kozlowski
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=36c4cd5f263e4bae22a1779a9befd24dacd5d3bf.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=angelogioacchino.delregno@collabora.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=robh@kernel.org \
--cc=rosenp@gmail.com \
--cc=stf_xl@wp.pl \
--cc=tsbogend@alpha.franken.de \
/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).