From: Kalle Valo <kvalo@kernel.org>
To: Conor Dooley <conor@kernel.org>
Cc: Ajay.Kathat@microchip.com, alexis.lothore@bootlin.com,
davidm@egauge.net, linux-wireless@vger.kernel.org,
claudiu.beznea@tuxon.dev, thomas.petazzoni@bootlin.com,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH RFC] wifi: wilc1000: fix reset line assert/deassert polarity
Date: Fri, 16 Feb 2024 20:07:58 +0200 [thread overview]
Message-ID: <87h6i8cmf5.fsf@kernel.org> (raw)
In-Reply-To: <20240216-spinster-decade-e136ac3e72d0@spud> (Conor Dooley's message of "Fri, 16 Feb 2024 16:55:16 +0000")
Conor Dooley <conor@kernel.org> writes:
>> > So if I'm understanding the situation correctly Microchip's porting
>> > guide[1] doesn't match with kernel.org documentation[2]? I'm not the
>> > expert here but from my point of view the issue is clear: the code needs
>> > to follow kernel.org documentation[2], not external documentation.
>>
>> My point of view would definitely be that drivers in the mainline kernel
>> absolutely should respect the ABI defined in the dt-binding. What a vendor
>> decides to do in their own tree I suppose is their problem, but I would
>> advocate that vendor kernels would also respect the ABI from mainline.
>>
>> Looking a bit more closely at the porting guide, it contains other
>> properties that are not present in the dt-binding - undocumented
>> compatibles and a different enable gpio property for example.
>> I guess it (and the vendor version of the driver) never got updated when
>> wilc1000 supported landed in mainline?
>>
>> > I'll add devicetree list so hopefully people there can comment also,
>> > full patch available in [3].
>> >
>> > Alexis, if there are no more comments I'm in favor submitting the revert
>> > you mentioned.
>>
>> From a dt-bindings point of view, the aforementioned revert seems
>> correct and would be
>> Acked-by: Conor Dooley <conor.dooley@microchip.com>
>
> Maybe an R-b is more suitable here, too used to acking trivial patches
> that are dt related..
On the contrary, I think Acked-by is the right thing here and makes it
easier for Alexis and me. Thanks!
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2024-02-16 18:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240213-wilc_1000_reset_line-v1-1-e01da2b23fed@bootlin.com>
[not found] ` <2ff1c701f3443e1c612a81f4077b0280850f57c6.camel@egauge.net>
[not found] ` <081bce96-f485-414c-8051-e1c14271f8cc@bootlin.com>
[not found] ` <aac398e4-d870-4ba2-8877-b98afecb8d1b@microchip.com>
2024-02-16 16:01 ` [PATCH RFC] wifi: wilc1000: fix reset line assert/deassert polarity Kalle Valo
2024-02-16 16:54 ` Conor Dooley
2024-02-16 16:55 ` Conor Dooley
2024-02-16 18:07 ` Kalle Valo [this message]
2024-02-17 0:10 ` Ajay.Kathat
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=87h6i8cmf5.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=Ajay.Kathat@microchip.com \
--cc=alexis.lothore@bootlin.com \
--cc=claudiu.beznea@tuxon.dev \
--cc=conor@kernel.org \
--cc=davidm@egauge.net \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=thomas.petazzoni@bootlin.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).