From: David Heidelberg <david@ixit.cz>
To: Yibo Wang <wyibo6109@gmail.com>
Cc: Mauro Carvalho Chehab <mchehab@kernel.org>,
linux-media@vger.kernel.org, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Daniel Scally <dan.scally@ideasonboard.com>,
Sakari Ailus <sakari.ailus@linux.intel.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: media: i2c: dongwoon,dw9719: Document DW9714VA
Date: Fri, 16 Oct 2026 23:03:37 +0200 [thread overview]
Message-ID: <2abeac6e-226e-4fcb-aa6e-e0f89af27251@ixit.cz> (raw)
In-Reply-To: <CALQ9cS49UzOPA8PUh8Yf55+D5oim=9YRF9iHw0Hi0sXuZFDTVw@mail.gmail.com>
On 16/10/2026 18:04, Yibo Wang wrote:
> Thanks, sorry for the trouble caused by my insufficient checking.
> I did use an LLM to organize register tables for the binding and clean-room
> HAL user space drivers work when I find my chip acts differently. I
Just today noticed that Assisted-by tag got removed from docs, so no need to do
it anymore.
> focused too much on C files and neglected docs.I will treat documents
> more seriously in future patches. Since this chip is common and someone
> will inevitably do a better job, I won't send a v2. Please feel free to
> drop this series. Sorry for the noise.
If you care about the device, send the v2 with updated wording.
If you don't do it, usually no-one does.
David
prev parent reply other threads:[~2026-10-16 21:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-16 9:09 [PATCH 1/2] dt-bindings: media: i2c: dongwoon,dw9719: Document DW9714VA wyibo6109
2026-10-16 9:09 ` [PATCH 2/2] media: i2c: dw9719: Add DW9714VA support wyibo6109
2026-10-16 9:18 ` sashiko-bot
2026-10-16 9:18 ` [PATCH 1/2] dt-bindings: media: i2c: dongwoon,dw9719: Document DW9714VA sashiko-bot
2026-10-16 13:03 ` Rob Herring (Arm)
2026-10-16 13:11 ` David Heidelberg
2026-10-16 16:04 ` Yibo Wang
2026-10-16 21:03 ` David Heidelberg [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=2abeac6e-226e-4fcb-aa6e-e0f89af27251@ixit.cz \
--to=david@ixit.cz \
--cc=conor+dt@kernel.org \
--cc=dan.scally@ideasonboard.com \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=robh@kernel.org \
--cc=sakari.ailus@linux.intel.com \
--cc=wyibo6109@gmail.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