From: Alexander Stein <alexander.stein@ew.tq-group.com>
To: Mark Brown <broonie@kernel.org>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
alsa-devel@alsa-project.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v2 1/1] ASoC: dt-bindings: tlv320aic32x4: convert to DT schema format
Date: Fri, 16 Jun 2023 14:24:17 +0200 [thread overview]
Message-ID: <24617723.6Emhk5qWAg@steina-w> (raw)
In-Reply-To: <3ddb3d09-2a9b-4a25-8108-a79ea83a9dd5@sirena.org.uk>
Hi Mark,
Am Freitag, 16. Juni 2023, 14:21:29 CEST schrieb Mark Brown:
> On Fri, Jun 16, 2023 at 02:17:40PM +0200, Alexander Stein wrote:
> > Am Freitag, 16. Juni 2023, 13:54:49 CEST schrieb Mark Brown:
> > > This doesn't apply against current code, please check and resend. This
> > > should be an incremental patch perhaps?
> >
> > Is there any change to original .txt file I am not aware of? The to be
> > created .yaml file is new, so there is no increment.
>
> That'll be the issue, yes.
Ok, there is nothing I can do, right?
> > To which base/branch/tag should I rebase this?
>
> As ever
>
> https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git
> for-next
As mentioned in the changelog, that's already the case.
Thanks and best regards,
Alexander
--
TQ-Systems GmbH | Mühlstraße 2, Gut Delling | 82229 Seefeld, Germany
Amtsgericht München, HRB 105018
Geschäftsführer: Detlef Schneider, Rüdiger Stahl, Stefan Schneider
http://www.tq-group.com/
next prev parent reply other threads:[~2023-06-16 12:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-16 8:35 [PATCH v2 1/1] ASoC: dt-bindings: tlv320aic32x4: convert to DT schema format Alexander Stein
2023-06-16 9:34 ` Krzysztof Kozlowski
2023-06-16 11:54 ` Mark Brown
2023-06-16 12:17 ` Alexander Stein
2023-06-16 12:21 ` Mark Brown
2023-06-16 12:24 ` Alexander Stein [this message]
2023-06-16 12:30 ` Mark Brown
2023-06-16 13:22 ` Alexander Stein
2023-06-16 13:37 ` Mark Brown
2023-06-16 16:17 ` 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=24617723.6Emhk5qWAg@steina-w \
--to=alexander.stein@ew.tq-group.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=robh+dt@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.