From: Charles Keepax <ckeepax@opensource.cirrus.com>
To: Andy Shevchenko <andriy.shevchenko@intel.com>
Cc: broonie@kernel.org, brgl@bgdev.pl, linus.walleij@linaro.org,
andy@kernel.org, p.zabel@pengutronix.de,
linux-gpio@vger.kernel.org, linux-spi@vger.kernel.org,
bartosz.golaszewski@linaro.org, linux-kernel@vger.kernel.org,
patches@opensource.cirrus.com
Subject: Re: [PATCH v2] spi: cs42l43: Use actual ACPI firmware node for chip selects
Date: Thu, 20 Nov 2025 12:42:45 +0000 [thread overview]
Message-ID: <aR8MxX1g38dq62rI@opensource.cirrus.com> (raw)
In-Reply-To: <aR8AmhcY_y93O3GM@smile.fi.intel.com>
On Thu, Nov 20, 2025 at 01:50:50PM +0200, Andy Shevchenko wrote:
> On Thu, Nov 20, 2025 at 10:59:07AM +0000, Charles Keepax wrote:
> > + struct property_entry props[] = {
> > + PROPERTY_ENTRY_REF_ARRAY_LEN("cs-gpios", args, ARRAY_SIZE(args)),
>
> No need to open code PROPERTY_ENTRY_REF_ARRAY().
Sorry yes forgot to put that back when I switched back from the
dynamic allocated ones. Bart let me know if you want a v3, or
happy to let you fix this up when you pull it into your chain?
Thanks,
Charles
next prev parent reply other threads:[~2025-11-20 12:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-20 10:59 [PATCH v2] spi: cs42l43: Use actual ACPI firmware node for chip selects Charles Keepax
2025-11-20 11:21 ` Philipp Zabel
2025-11-20 12:27 ` Bartosz Golaszewski
2025-11-20 13:43 ` Bartosz Golaszewski
2025-11-20 11:50 ` Andy Shevchenko
2025-11-20 12:42 ` Charles Keepax [this message]
2025-11-20 12:48 ` Bartosz Golaszewski
2025-11-21 6:53 ` kernel test robot
2025-11-21 19:36 ` kernel test robot
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=aR8MxX1g38dq62rI@opensource.cirrus.com \
--to=ckeepax@opensource.cirrus.com \
--cc=andriy.shevchenko@intel.com \
--cc=andy@kernel.org \
--cc=bartosz.golaszewski@linaro.org \
--cc=brgl@bgdev.pl \
--cc=broonie@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=p.zabel@pengutronix.de \
--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