From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: "Heikki Krogerus" <heikki.krogerus@linux.intel.com>,
"Clément Léger" <clement.leger@bootlin.com>,
"Mauro Carvalho Chehab" <mchehab@kernel.org>,
"Daniel Scally" <djrscally@gmail.com>,
"Sakari Ailus" <sakari.ailus@linux.intel.com>,
"Hans de Goede" <hdegoede@redhat.com>,
linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-media@vger.kernel.org
Subject: Re: [PATCH v2 1/4] media: ipu3-cio2: Don't dereference fwnode handle
Date: Wed, 23 Nov 2022 20:01:57 +0200 [thread overview]
Message-ID: <Y35gFZ7aK9JIrUWy@smile.fi.intel.com> (raw)
In-Reply-To: <20221121152704.30180-1-andriy.shevchenko@linux.intel.com>
+ Cc: Petr, Sergey
On Mon, Nov 21, 2022 at 05:27:01PM +0200, Andy Shevchenko wrote:
> Use acpi_fwnode_handle() instead of dereferencing an fwnode handle directly,
> which is a better coding practice.
It appears that this series depends on fd070e8ceb90 ("test_printf: Refactor
fwnode_pointer() to make it more readable") which is in PRINTK tree.
Sakari, Mauro, if you are okay to route this via that tree, can we get your
tags for that? Otherwise we need to postpone this till v6.2-rc1 (but I would
like to decrease the chances to appear a new user of the to be removed API).
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2022-11-23 18:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-21 15:27 [PATCH v2 1/4] media: ipu3-cio2: Don't dereference fwnode handle Andy Shevchenko
2022-11-21 15:27 ` [PATCH v2 2/4] media: ipu3-cio2: Convert to use software_node_register_node_group() Andy Shevchenko
2022-11-21 15:27 ` [PATCH v2 3/4] software node: Switch property entry test to a new API Andy Shevchenko
2022-11-21 15:27 ` [PATCH v2 4/4] software node: Remove unused APIs Andy Shevchenko
2022-11-23 18:01 ` Andy Shevchenko [this message]
2022-11-23 19:10 ` [PATCH v2 1/4] media: ipu3-cio2: Don't dereference fwnode handle Andy Shevchenko
2022-12-07 9:02 ` Sakari Ailus
2022-12-07 9:53 ` Andy Shevchenko
2022-12-07 14:00 ` Sakari Ailus
2022-12-08 10:35 ` Petr Mladek
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=Y35gFZ7aK9JIrUWy@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=clement.leger@bootlin.com \
--cc=djrscally@gmail.com \
--cc=hdegoede@redhat.com \
--cc=heikki.krogerus@linux.intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=sakari.ailus@linux.intel.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