From: "Karel Balej" <balejk@matfyz.cz>
To: "Brian Norris" <briannorris@chromium.org>
Cc: "Francesco Dolcini" <francesco@dolcini.it>,
"Johannes Berg" <johannes@sipsolutions.net>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Duje Mihanović" <duje@dujemihanovic.xyz>,
"Andrew Lunn" <andrew@lunn.ch>,
"Gregory Clement" <gregory.clement@bootlin.com>,
"Sebastian Hesselbarth" <sebastian.hesselbarth@gmail.com>,
"Ulf Hansson" <ulf.hansson@linaro.org>,
"Frank Li" <Frank.Li@nxp.com>,
linux-wireless@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-mmc@vger.kernel.org,
~postmarketos/upstreaming@lists.sr.ht,
phone-devel@vger.kernel.org, "Jeff Chen" <jeff.chen_1@nxp.com>,
"Peng Fan" <peng.fan@nxp.com>,
david@ixit.cz
Subject: Re: [DONOTAPPLY RFC PATCH v2 0/4] WiFi support for samsung,coreprimevelte
Date: Wed, 29 Apr 2026 20:36:26 +0200 [thread overview]
Message-ID: <DI5UU03J2IU3.61E7OU85TZJH@matfyz.cz> (raw)
In-Reply-To: <afI8y70U7wFT_07h@google.com>
Brian Norris, 2026-04-29T10:15:55-07:00:
>> and it would be great to not have to keep the
>> patches in a fork, especially when trying to build on top of them
>> further (such as to fix the driver-firmware incompatibilities discussed
>> in one of the patches of this series).
>
> Patch 3 is a different story. At the moment, it's definitely not
> acceptable. But I tried to provide hints about how you can write proper
> FW compatibility logic. I'm still not optimistic that'll be easy and
> maintainable, and we still reserve the right to reject patches if they
> make things unmaintainable.
I was referring to the original patches here, I would of course modify
the compability patch according to your feedback, I just didn't want to
invest the effort into that when it wasn't and still isn't clear if it
will ever be possible to upstream it.
I'm curious to hear from Johannes now then.
Thank you for the information,
Karel
prev parent reply other threads:[~2026-04-29 18:36 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-26 18:20 [DONOTAPPLY RFC PATCH v2 0/4] WiFi support for samsung,coreprimevelte Karel Balej
2025-10-26 18:20 ` [DONOTAPPLY RFC PATCH v2 1/4] dt-bindings: mwifiex: document use with the SD8777 chipset Karel Balej
2025-12-03 21:50 ` Brian Norris
2025-10-26 18:20 ` [DONOTAPPLY RFC PATCH v2 2/4] net: mwifiex: add support for " Karel Balej
2025-10-26 18:20 ` [DONOTAPPLY RFC PATCH v2 3/4] DONOTMERGE: net: mwifiex: fix timeouts with the SD8777 chip Karel Balej
2025-12-03 21:46 ` Brian Norris
2025-10-26 18:20 ` [DONOTAPPLY RFC PATCH v2 4/4] arm64: dts: samsung,coreprimevelte: add wifi node Karel Balej
2025-12-03 21:47 ` Brian Norris
2025-12-12 8:36 ` Karel Balej
2025-12-12 14:55 ` Duje Mihanović
2025-12-12 21:17 ` Karel Balej
2025-12-12 22:44 ` Duje Mihanović
2025-11-27 15:29 ` [DONOTAPPLY RFC PATCH v2 0/4] WiFi support for samsung,coreprimevelte Karel Balej
2025-11-28 17:05 ` Francesco Dolcini
2025-12-01 16:25 ` Karel Balej
2026-04-29 10:55 ` Karel Balej
2026-04-29 11:22 ` Francesco Dolcini
2026-04-29 13:20 ` Karel Balej
2026-04-29 13:40 ` Francesco Dolcini
2026-04-29 13:47 ` Karel Balej
2026-04-29 17:15 ` Brian Norris
2026-04-29 18:36 ` Karel Balej [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=DI5UU03J2IU3.61E7OU85TZJH@matfyz.cz \
--to=balejk@matfyz.cz \
--cc=Frank.Li@nxp.com \
--cc=andrew@lunn.ch \
--cc=briannorris@chromium.org \
--cc=conor+dt@kernel.org \
--cc=david@ixit.cz \
--cc=devicetree@vger.kernel.org \
--cc=duje@dujemihanovic.xyz \
--cc=francesco@dolcini.it \
--cc=gregory.clement@bootlin.com \
--cc=jeff.chen_1@nxp.com \
--cc=johannes@sipsolutions.net \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=peng.fan@nxp.com \
--cc=phone-devel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=sebastian.hesselbarth@gmail.com \
--cc=ulf.hansson@linaro.org \
--cc=~postmarketos/upstreaming@lists.sr.ht \
/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