From: Andy Shevchenko <andy.shevchenko@gmail.com>
To: Charles Keepax <ckeepax@opensource.cirrus.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 v6 2/4] spi: Switch to using is_acpi_device_node() in spi_dev_set_name()
Date: Mon, 15 Apr 2024 19:06:56 +0300 [thread overview]
Message-ID: <CAHp75VdGq8L5ZQxo0BrC-TevY+pP2s0ZYkHcefjROvpf1+5MNw@mail.gmail.com> (raw)
In-Reply-To: <20240415140925.3518990-3-ckeepax@opensource.cirrus.com>
On Mon, Apr 15, 2024 at 5:09 PM Charles Keepax
<ckeepax@opensource.cirrus.com> wrote:
>
> Use is_acpi_device_node() rather than checking ACPI_COMPANION(), such
> that when checking for other types of firmware node the code can
a firmware node
> consistently do checks against the fwnode.
Reviewed-by: Andy Shevchenko <andy.shevchenko@gmail.com>
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2024-04-15 16:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-15 14:09 [PATCH v6 0/4] Add bridged amplifiers to cs42l43 Charles Keepax
2024-04-15 14:09 ` [PATCH v6 1/4] gpio: swnode: Add ability to specify native chip selects for SPI Charles Keepax
2024-04-15 16:05 ` Andy Shevchenko
2024-04-16 21:09 ` Bartosz Golaszewski
2024-04-15 14:09 ` [PATCH v6 2/4] spi: Switch to using is_acpi_device_node() in spi_dev_set_name() Charles Keepax
2024-04-15 16:06 ` Andy Shevchenko [this message]
2024-04-16 9:53 ` Charles Keepax
2024-04-15 14:09 ` [PATCH v6 3/4] spi: Update swnode based SPI devices to use the fwnode name Charles Keepax
2024-04-15 16:09 ` Andy Shevchenko
2024-04-15 14:09 ` [PATCH v6 4/4] spi: cs42l43: Add bridged cs35l56 amplifiers Charles Keepax
2024-04-15 16:17 ` Andy Shevchenko
2024-04-16 9:54 ` Charles Keepax
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=CAHp75VdGq8L5ZQxo0BrC-TevY+pP2s0ZYkHcefjROvpf1+5MNw@mail.gmail.com \
--to=andy.shevchenko@gmail.com \
--cc=bard.liao@intel.com \
--cc=brgl@bgdev.pl \
--cc=broonie@kernel.org \
--cc=ckeepax@opensource.cirrus.com \
--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 read-only IMAP folder(s) and NNTP newsgroup(s).