From: Krzysztof Kozlowski <krzk@kernel.org>
To: Shreeya Patel <shreeya.patel@collabora.com>, Marek Vasut <marex@denx.de>
Cc: linux-iio@vger.kernel.org, Conor Dooley <conor+dt@kernel.org>,
Jonathan Cameron <jic23@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: Sun, 7 Jul 2024 14:02:39 +0200 [thread overview]
Message-ID: <98992b1d-c94a-4053-a755-32a25d7fdc46@kernel.org> (raw)
In-Reply-To: <3b2ca0-6687ce00-3-4dab7280@52083650>
On 05/07/2024 12:42, Shreeya Patel wrote:
> On Friday, July 05, 2024 15:20 IST, Marek Vasut <marex@denx.de> wrote:
>
>> The "ltr,ltrf216a" compatible string is not documented in DT binding
>> document, remove it.
>>
>> Signed-off-by: Marek Vasut <marex@denx.de>
>> ---
>> Cc: Conor Dooley <conor+dt@kernel.org>
>> Cc: Jonathan Cameron <jic23@kernel.org>
>> Cc: Krzysztof Kozlowski <krzk+dt@kernel.org>
>> Cc: Lars-Peter Clausen <lars@metafoo.de>
>> Cc: Marek Vasut <marex@denx.de>
>> Cc: Rob Herring <robh@kernel.org>
>> Cc: Shreeya Patel <shreeya.patel@collabora.com>
>> Cc: devicetree@vger.kernel.org
>> Cc: linux-iio@vger.kernel.org
>> ---
>> drivers/iio/light/ltrf216a.c | 1 -
>> 1 file changed, 1 deletion(-)
>>
>> diff --git a/drivers/iio/light/ltrf216a.c b/drivers/iio/light/ltrf216a.c
>> index 68dc48420a886..78fc910fcb18c 100644
>> --- a/drivers/iio/light/ltrf216a.c
>> +++ b/drivers/iio/light/ltrf216a.c
>> @@ -528,7 +528,6 @@ MODULE_DEVICE_TABLE(i2c, ltrf216a_id);
>>
>> static const struct of_device_id ltrf216a_of_match[] = {
>> { .compatible = "liteon,ltrf216a" },
>> - { .compatible = "ltr,ltrf216a" },
>> {}
>
> This compatible string with a different vendor prefix was added for a specific reason.
> Please see the commit message of the following patch :-
> https://lore.kernel.org/all/20220511094024.175994-2-shreeya.patel@collabora.com/
And adding this specific compatible was clearly NAKed:
https://lore.kernel.org/all/20220516170406.GB2825626-robh@kernel.org/
yet you still added it. That's a deliberate going around maintainer's
decision.
>
> We were very well aware that not documenting this was going to generate a warning so
You *CANNOT* have undocumented compatibles.
> we tried to fix that with a deprecated tag but it was NAKd by Rob. What we understood
Because the driver was NAKed obviously as well.
> from his last message was that it wasn't necessary to fix the DT warning.
I am quite angry that maintainer tells you something, but you push your
patch through because apparently you need to fulfill your project
requirements.
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-07-07 12:02 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 [this message]
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
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=98992b1d-c94a-4053-a755-32a25d7fdc46@kernel.org \
--to=krzk@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jic23@kernel.org \
--cc=kernel@collabora.com \
--cc=krzk+dt@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).