From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: linux-media@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Mauro Carvalho Chehab <mchehab@kernel.org>
Subject: Re: [PATCH v3 1/1] media: v4l2-core: Replace the check for firmware registered I2C devices
Date: Fri, 14 Mar 2025 19:16:16 +0200 [thread overview]
Message-ID: <Z9RkYCJ-ggJl2kn0@smile.fi.intel.com> (raw)
In-Reply-To: <20250313113115.359942-1-andriy.shevchenko@linux.intel.com>
On Thu, Mar 13, 2025 at 01:30:34PM +0200, Andy Shevchenko wrote:
> Replace the check for firmware registered I²C devices as the firmware node
> independently on type should be retrieved via dev_fwnode().
Hans, are you okay with this now? Can it be applied?
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2025-03-14 17:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-13 11:30 [PATCH v3 1/1] media: v4l2-core: Replace the check for firmware registered I2C devices Andy Shevchenko
2025-03-14 17:16 ` Andy Shevchenko [this message]
2025-04-08 12:17 ` Andy Shevchenko
2025-05-02 14:14 ` 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=Z9RkYCJ-ggJl2kn0@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@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