From: Stephen Kitt <steve@sk2.org>
To: Mark Brown <broonie@kernel.org>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
patches@opensource.cirrus.com, Wolfram Sang <wsa@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ASoC: wm*: use simple i2c probe function
Date: Fri, 25 Mar 2022 18:26:16 +0100 [thread overview]
Message-ID: <20220325182616.6fb6e13e@heffalump.sk2.org> (raw)
In-Reply-To: <Yj34gLRxhmXD1Y5B@sirena.org.uk>
[-- Attachment #1: Type: text/plain, Size: 810 bytes --]
On Fri, 25 Mar 2022 17:14:40 +0000, Mark Brown <broonie@kernel.org> wrote:
> On Fri, Mar 25, 2022 at 05:24:39PM +0100, Stephen Kitt wrote:
> > The i2c probe functions here don't use the id information provided in
> > their second argument, so the single-parameter i2c probe function
> > ("probe_new") can be used instead.
>
> This is going to generate conflicts with other pending and more
> substantial patches for wm8731 - please resubmit after those have been
> applied, or split up into finer grained patches so the rest can go.
Ah right, I’ll re-submit without wm8731.
Which tree should I check for conflicts? I’ve got similar patches across all
the i2c-using sound/soc/codecs files, I wouldn’t want to waste anyone’s time
if I can check beforehand...
Regards,
Stephen
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-03-25 17:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-25 16:24 Stephen Kitt
2022-03-25 17:14 ` Mark Brown
2022-03-25 17:26 ` Stephen Kitt [this message]
2022-03-25 17:38 ` Mark Brown
2022-03-25 17:51 ` Stephen Kitt
2022-03-25 17:56 ` Mark Brown
2022-03-30 9:34 ` Wolfram Sang
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=20220325182616.6fb6e13e@heffalump.sk2.org \
--to=steve@sk2.org \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@opensource.cirrus.com \
--cc=wsa@kernel.org \
/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
all inboxes | Powered by JetHome®