From: Charles Keepax <ckeepax@opensource.cirrus.com>
To: Mark Brown <broonie@kernel.org>
Cc: <linux-spi@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<patches@opensource.cirrus.com>
Subject: Re: [PATCH v2 1/2] spi: cs42l43: Refactor accessing the SDCA extension properties
Date: Wed, 19 Jun 2024 14:26:36 +0100 [thread overview]
Message-ID: <ZnLcjO67FH2weX+y@opensource.cirrus.com> (raw)
In-Reply-To: <171880144842.113265.13864100805243474696.b4-ty@kernel.org>
On Wed, Jun 19, 2024 at 01:50:48PM +0100, Mark Brown wrote:
> On Wed, 19 Jun 2024 13:17:02 +0100, Charles Keepax wrote:
> > Refactor accessing the SDCA extension properties to make it easier to
> > access multiple properties to assist with future features. Return the
> > node itself and allow the caller to read the actual properties.
> >
> >
>
> Applied to
>
> https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next
>
> Thanks!
>
> [1/2] spi: cs42l43: Refactor accessing the SDCA extension properties
> commit: 6914ee9cd1b0c91bd2fb4dbe204947c3c31259e1
> [2/2] spi: cs42l43: Add speaker id support to the bridge configuration
> (no commit info)
>
Not sure all went smoothly here. This seems to have picked up v1
of the first patch and not picked up the second one.
Thanks,
Charles
next prev parent reply other threads:[~2024-06-19 13:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-19 12:17 [PATCH v2 1/2] spi: cs42l43: Refactor accessing the SDCA extension properties Charles Keepax
2024-06-19 12:17 ` [PATCH v2 2/2] spi: cs42l43: Add speaker id support to the bridge configuration Charles Keepax
2024-06-19 12:50 ` [PATCH v2 1/2] spi: cs42l43: Refactor accessing the SDCA extension properties Mark Brown
2024-06-19 13:26 ` Charles Keepax [this message]
2024-06-19 13:30 ` Mark Brown
2024-06-19 13:40 ` Charles Keepax
2024-06-19 13:44 ` Mark Brown
2024-06-19 13:47 ` Charles Keepax
2024-06-19 13:56 ` Mark Brown
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=ZnLcjO67FH2weX+y@opensource.cirrus.com \
--to=ckeepax@opensource.cirrus.com \
--cc=broonie@kernel.org \
--cc=linux-kernel@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