From: Lee Jones <lee@kernel.org>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Daniel Thompson <daniel.thompson@linaro.org>,
dri-devel@lists.freedesktop.org, linux-fbdev@vger.kernel.org,
linux-kernel@vger.kernel.org, Jingoo Han <jingoohan1@gmail.com>,
Helge Deller <deller@gmx.de>
Subject: Re: [PATCH v2 0/4] backlight: hx8357: Clean up and make OF-independent
Date: Thu, 8 Feb 2024 17:10:14 +0000 [thread overview]
Message-ID: <20240208171014.GW689448@google.com> (raw)
In-Reply-To: <ZcUKmlbtyktnKhLr@smile.fi.intel.com>
On Thu, 08 Feb 2024, Andy Shevchenko wrote:
> On Thu, Feb 08, 2024 at 10:53:04AM +0000, Lee Jones wrote:
> > On Thu, 01 Feb 2024, Andy Shevchenko wrote:
>
> ...
>
> > Someone may wish to address this:
> >
> > WARNING: DT compatible string "himax,hx8369" appears un-documented -- check ./Documentation/devicetree/bindings/
> > #58: FILE: drivers/video/backlight/hx8357.c:636:
> > + .compatible = "himax,hx8369",
>
> I can do it if and when have more time. But apparently it was before this
> series, right?
I'm not sure it's ever been documented.
It doesn't affect your series in any way.
--
Lee Jones [李琼斯]
prev parent reply other threads:[~2024-02-08 17:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-01 14:47 [PATCH v2 0/4] backlight: hx8357: Clean up and make OF-independent Andy Shevchenko
2024-02-01 14:47 ` [PATCH v2 1/4] backlight: hx8357: Make use of device properties Andy Shevchenko
2024-02-02 10:17 ` Daniel Thompson
2024-02-01 14:47 ` [PATCH v2 2/4] backlight: hx8357: Move OF table closer to its consumer Andy Shevchenko
2024-02-01 14:47 ` [PATCH v2 3/4] backlight: hx8357: Make use of dev_err_probe() Andy Shevchenko
2024-02-01 14:47 ` [PATCH v2 4/4] backlight: hx8357: Utilise temporary variable for struct device Andy Shevchenko
2024-02-08 10:52 ` [PATCH v2 0/4] backlight: hx8357: Clean up and make OF-independent Lee Jones
2024-02-08 10:53 ` Lee Jones
2024-02-08 17:08 ` Andy Shevchenko
2024-02-08 17:10 ` Lee Jones [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=20240208171014.GW689448@google.com \
--to=lee@kernel.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=daniel.thompson@linaro.org \
--cc=deller@gmx.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=jingoohan1@gmail.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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).