From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Jonathan Cameron <jic23@kernel.org>
Cc: Krzysztof Kozlowski <krzk@kernel.org>,
Shreeya Patel <shreeya.patel@collabora.com>,
Marek Vasut <marex@denx.de>,
linux-iio@vger.kernel.org, Conor Dooley <conor+dt@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Lars-Peter Clausen <lars@metafoo.de>,
Rob Herring <robh@kernel.org>,
devicetree@vger.kernel.org, kernel@collabora.com
Subject: Re: [PATCH] iio: light: ltrf216a: Drop undocumented ltr,ltrf216a compatible string
Date: Mon, 12 Aug 2024 16:24:20 +0300 [thread overview]
Message-ID: <ZroNBIx61KKzcKQc@smile.fi.intel.com> (raw)
In-Reply-To: <20240707143759.7718e0f3@jic23-huawei>
On Sun, Jul 07, 2024 at 02:37:59PM +0100, Jonathan Cameron wrote:
> On Sun, 7 Jul 2024 14:02:39 +0200
> Krzysztof Kozlowski <krzk@kernel.org> wrote:
...
> So, I don't see this as a deliberate attempt to bypass a maintainer Nack.
> I'd love to be in a position to say no on ACPI bindings that are garbage
> (there are a lot of them) but Windows is dominant in that space so
> we get stuck with their mess.
...and we are trying hard to avoid this mess in the future (e.g., what is
happening to MIPI I3C case nowadays).
Unfortunately Linux world seems not being so interested in this topic either
(as my proposal to discuss the ACPI ID topic on LPC has been rejected).
> On server's it is a different game
> and the kernel community regularly gets significant changes made.
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2024-08-12 13:24 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-05 9:50 [PATCH] iio: light: ltrf216a: Drop undocumented ltr,ltrf216a compatible string Marek Vasut
2024-07-05 9:55 ` Krzysztof Kozlowski
2024-07-05 10:42 ` Shreeya Patel
2024-07-05 14:52 ` Marek Vasut
2024-07-05 18:03 ` Shreeya Patel
2024-07-07 11:26 ` Jonathan Cameron
2024-07-07 12:06 ` Krzysztof Kozlowski
2024-07-07 13:43 ` Jonathan Cameron
2024-07-07 12:02 ` Krzysztof Kozlowski
2024-07-07 13:37 ` Jonathan Cameron
2024-07-07 13:46 ` Krzysztof Kozlowski
2024-07-07 14:08 ` Jonathan Cameron
2024-07-08 11:25 ` Krzysztof Kozlowski
2024-07-08 12:29 ` Sebastian Reichel
2024-07-08 12:13 ` Sebastian Reichel
2024-07-08 13:20 ` Shreeya Patel
2024-07-08 16:01 ` Jonathan Cameron
2024-08-12 13:24 ` Andy Shevchenko [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=ZroNBIx61KKzcKQc@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jic23@kernel.org \
--cc=kernel@collabora.com \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=marex@denx.de \
--cc=robh@kernel.org \
--cc=shreeya.patel@collabora.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 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).