From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
linux-pwm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 1/1] pwm: core: Replace custom implementation of device_match_fwnode()
Date: Wed, 28 Sep 2022 17:49:36 +0300 [thread overview]
Message-ID: <YzRfAE58ZMI/MC0K@smile.fi.intel.com> (raw)
In-Reply-To: <YzRZp4e48XK6jAZD@orome>
On Wed, Sep 28, 2022 at 04:26:47PM +0200, Thierry Reding wrote:
> On Tue, Sep 27, 2022 at 08:22:58PM +0300, Andy Shevchenko wrote:
> > Replace custom implementation of the device_match_fwnode().
> I really don't see the point in having an exported symbol for this. It's
> a simple comparison and the result is even longer than the original.
Longer doesn't always mean worse.
> The
> *only* reason why this helper exists seems to be because it is getting
> used in *_find_device() callbacks.
Yes and no. Initially for the purpose to be a callback it can be reused.
The point is that it hides the dev_fwnode() machinery behind and taking
into account ongoing discussion about constification of the dev_fwnode()
we might need to touch this or similar places to avoid problems with
compiler.
> Honestly, I don't see a reason why this should be applied. And frankly,
> why bother making all these changes. It's a waste of time, in my
> opinion.
Obviously I will not do it if I be with you on the same page.
But okay, not a big deal in this case.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2022-09-28 14:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-27 17:22 [PATCH v1 1/1] pwm: core: Replace custom implementation of device_match_fwnode() Andy Shevchenko
2022-09-28 14:26 ` Thierry Reding
2022-09-28 14:49 ` Andy Shevchenko [this message]
2022-09-28 14:57 ` Thierry Reding
2022-09-28 15:40 ` 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=YzRfAE58ZMI/MC0K@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=thierry.reding@gmail.com \
--cc=u.kleine-koenig@pengutronix.de \
/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