From: Markus Probst <markus.probst@posteo.de>
To: "Krzysztof Kozlowski" <krzk@kernel.org>,
"Hans de Goede" <hansg@kernel.org>,
"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
"Bryan O'Donoghue" <bryan.odonoghue@linaro.org>,
"Lee Jones" <lee@kernel.org>, "Pavel Machek" <pavel@kernel.org>,
"Miguel Ojeda" <ojeda@kernel.org>,
"Boqun Feng" <boqun@kernel.org>, "Gary Guo" <gary@garyguo.net>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Benno Lossin" <lossin@kernel.org>,
"Andreas Hindborg" <a.hindborg@kernel.org>,
"Alice Ryhl" <aliceryhl@google.com>,
"Trevor Gross" <tmgross@umich.edu>,
"Danilo Krummrich" <dakr@kernel.org>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>
Cc: platform-driver-x86@vger.kernel.org, linux-leds@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
rust-for-linux@vger.kernel.org
Subject: Re: [PATCH v8 2/2] platform: Add initial synology microp driver
Date: Tue, 21 Apr 2026 16:29:53 +0000 [thread overview]
Message-ID: <7bb65d98aad028bd4f430985b617d4cb61b31032.camel@posteo.de> (raw)
In-Reply-To: <00486b10-4c0b-420b-a735-67c3164eeb24@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 1249 bytes --]
On Tue, 2026-04-21 at 17:33 +0200, Krzysztof Kozlowski wrote:
> On 20/04/2026 16:24, Markus Probst wrote:
> > + // pineview
> > + (DeviceId::new(c"synology,ds710p-microp"), Model::new().led_esata()),
> > + (DeviceId::new(c"synology,ds1010p-microp"), Model::new().led_alert(Color::Orange)),
> > + (DeviceId::new(c"synology,ds411p-microp"), Model::new()),
> > +
> > + // r1000
> > + (DeviceId::new(c"synology,ds923p-microp"), Model::new()),
> > + (DeviceId::new(c"synology,ds723p-microp"), Model::new()),
> > + (DeviceId::new(c"synology,ds1522p-microp"), Model::new()),
>
> What is this all doing here? Again, what is the fallback and front
> compatible?
>
See previous comment. There was no separation between them until now. I
will fix that.
> Why do you keep duplicating all this when I asked to REMOVE
> the completely unnecessary front compatibles?
I can't recall you asking that. My apologies if I missed that.
So only keep the fallbacks and only add a front compatible if a
unexpected difference comes up?
Thanks
- Markus Probst
>
> So it is not only schema which is wrong, but your driver makes no sense
> with it.
>
> Best regards,
> Krzysztof
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 870 bytes --]
next prev parent reply other threads:[~2026-04-21 16:29 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-20 14:24 [PATCH v8 0/2] Introduce Synology Microp driver Markus Probst
2026-04-20 14:24 ` [PATCH v8 1/2] dt-bindings: embedded-controller: Add synology microp devices Markus Probst
2026-04-21 7:07 ` Krzysztof Kozlowski
2026-04-21 14:50 ` Markus Probst
2026-04-21 15:32 ` Krzysztof Kozlowski
2026-04-21 16:25 ` Markus Probst
2026-04-23 9:38 ` Krzysztof Kozlowski
2026-04-20 14:24 ` [PATCH v8 2/2] platform: Add initial synology microp driver Markus Probst
2026-04-21 11:59 ` Ilpo Järvinen
2026-04-21 14:17 ` Markus Probst
2026-04-21 14:58 ` Miguel Ojeda
2026-04-21 18:10 ` Ilpo Järvinen
2026-04-21 18:20 ` Markus Probst
2026-04-21 18:36 ` Ilpo Järvinen
2026-04-21 18:46 ` Miguel Ojeda
2026-04-22 13:48 ` FUJITA Tomonori
2026-04-21 15:33 ` Krzysztof Kozlowski
2026-04-21 16:29 ` Markus Probst [this message]
2026-04-20 15:55 ` [PATCH v8 0/2] Introduce Synology Microp driver Markus Probst
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=7bb65d98aad028bd4f430985b617d4cb61b31032.camel@posteo.de \
--to=markus.probst@posteo.de \
--cc=a.hindborg@kernel.org \
--cc=aliceryhl@google.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun@kernel.org \
--cc=bryan.odonoghue@linaro.org \
--cc=conor+dt@kernel.org \
--cc=dakr@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gary@garyguo.net \
--cc=gregkh@linuxfoundation.org \
--cc=hansg@kernel.org \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=lee@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=lossin@kernel.org \
--cc=ojeda@kernel.org \
--cc=pavel@kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=robh@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=tmgross@umich.edu \
/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