From: Charles Keepax <ckeepax@opensource.cirrus.com>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: <broonie@kernel.org>, <linus.walleij@linaro.org>, <brgl@bgdev.pl>,
<bard.liao@intel.com>, <linux-gpio@vger.kernel.org>,
<linux-spi@vger.kernel.org>, <patches@opensource.cirrus.com>
Subject: Re: [PATCH v5 2/4] spi: Switch to using is_acpi_device_node() in spi_dev_set_name()
Date: Thu, 11 Apr 2024 16:56:16 +0000 [thread overview]
Message-ID: <ZhgWMK7HU2jmsmTq@ediswmail9.ad.cirrus.com> (raw)
In-Reply-To: <CAHp75VfAoKvvnQr74-rpJhEv=U=o00Doji-1zuV3-_+n+cbVVg@mail.gmail.com>
On Thu, Apr 11, 2024 at 04:30:13PM +0300, Andy Shevchenko wrote:
> On Thu, Apr 11, 2024 at 12:06 PM Charles Keepax
> <ckeepax@opensource.cirrus.com> wrote:
> >
> > Use the more modern is_acpi_device_node() rather than checking
> > ACPI_COMPANION().
>
> I don't think it's valuable on its own. There is no clear motivation
> why to do that, I suggested it exactly in the conjunction of not
> introducing two ways of fwnode type check. That said, you probably
> want to elaborate the motivation in the commit message if you want to
> keep it separate.
>
I am really tempted to just drop this, its not necessary for my
changes and changes something that is unrelated to them. At the
least it belongs in a separate patch.
> ...
>
> > +#include <linux/fwnode.h>
>
> This header is not supposed to be included by the end users. property.h is.
>
Fair enough will update, although I really feel these headers
could use some annotation if they are not supposed to be directly
included. Either include everything you use or just include a top
level header makes sense but this weird mixture we seem to use is
very confusing and I don't have a big enough brain to remember
every header.
Thanks,
Charles
next prev parent reply other threads:[~2024-04-11 16:56 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-11 9:06 [PATCH 0/4] Add bridged amplifiers to cs42l43 Charles Keepax
2024-04-11 9:06 ` [PATCH v5 1/4] gpio: swnode: Add ability to specify native chip selects for SPI Charles Keepax
2024-04-11 13:25 ` Andy Shevchenko
2024-04-11 16:44 ` Charles Keepax
2024-04-11 16:50 ` Andy Shevchenko
2024-04-11 16:58 ` Charles Keepax
2024-04-11 9:06 ` [PATCH v5 2/4] spi: Switch to using is_acpi_device_node() in spi_dev_set_name() Charles Keepax
2024-04-11 13:30 ` Andy Shevchenko
2024-04-11 16:56 ` Charles Keepax [this message]
2024-04-11 18:09 ` Andy Shevchenko
2024-04-11 9:06 ` [PATCH v5 3/4] spi: Update swnode based SPI devices to use the fwnode name Charles Keepax
2024-04-11 13:33 ` Andy Shevchenko
2024-04-11 17:04 ` Charles Keepax
2024-04-11 18:07 ` Andy Shevchenko
2024-04-11 9:06 ` [PATCH v5 4/4] spi: cs42l43: Add bridged cs35l56 amplifiers Charles Keepax
2024-04-11 14:04 ` Andy Shevchenko
2024-04-11 14:06 ` Andy Shevchenko
2024-04-11 14:07 ` Andy Shevchenko
2024-04-11 17:13 ` Charles Keepax
2024-04-11 18:17 ` Andy Shevchenko
2024-04-15 13:39 ` Charles Keepax
2024-04-15 16:03 ` Andy Shevchenko
2024-04-11 11:46 ` [PATCH 0/4] Add bridged amplifiers to cs42l43 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=ZhgWMK7HU2jmsmTq@ediswmail9.ad.cirrus.com \
--to=ckeepax@opensource.cirrus.com \
--cc=andy.shevchenko@gmail.com \
--cc=bard.liao@intel.com \
--cc=brgl@bgdev.pl \
--cc=broonie@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=patches@opensource.cirrus.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;
as well as URLs for NNTP newsgroup(s).