From: Mark Brown <broonie@kernel.org>
To: Andreas Axelsson <andreas.axelsson@androscientia.com>
Cc: lgirdwood@gmail.com, shenghao-ding@ti.com, kevin-lu@ti.com,
baojun.xu@ti.com, sen@ti.com, tiwai@suse.com,
linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] ASoC: tas2781: Skip calibration data for other SPI devices
Date: Tue, 29 Sep 2026 23:25:06 +0100 [thread overview]
Message-ID: <d0169d44-af4f-4ebf-9e55-371ac1ebe0fc@sirena.org.uk> (raw)
In-Reply-To: <e97bc4b2-69f7-4a71-8b32-9d3c60b2ca60@sirena.org.uk>
[-- Attachment #1: Type: text/plain, Size: 1108 bytes --]
On Tue, Sep 29, 2026 at 11:24:07PM +0100, Mark Brown wrote:
> On Tue, Sep 29, 2026 at 11:53:03PM +0200, Andreas Axelsson wrote:
>
> > v2:
> > - Rebased on current code. The tasdevice_process_block() part of v1
> > is superseded by commit 513480da5e9c; only the calibration part
> > remains.
>
> This applies on neither for-7.3 nor for-7.4 of:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git
>
> As a fix I'd expect to apply it on for-7.3. I'm also seeing a conflict
> against Linus' current tree.
BTW you might want to look into using b4 to send - looking again I see
it's not actually a conflict but rather a formatting issue:
Patch failed at 0001 ASoC: tas2781: Skip calibration data for other SPI devices
error: git diff header lacks filename information when removing 1 leading pathname component (line 13)
error: could not build fake ancestor
You might want to look at b4 to send the patches, especially it's web
submission endpoint which avoids having to configure mail:
https://b4.docs.kernel.org/en/latest/contributor/overview.html
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2026-09-29 22:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-29 21:53 Andreas Axelsson
2026-09-29 22:24 ` Mark Brown
2026-09-29 22:25 ` Mark Brown [this message]
2026-11-20 21:58 ` Ye Shu
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=d0169d44-af4f-4ebf-9e55-371ac1ebe0fc@sirena.org.uk \
--to=broonie@kernel.org \
--cc=andreas.axelsson@androscientia.com \
--cc=baojun.xu@ti.com \
--cc=kevin-lu@ti.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=sen@ti.com \
--cc=shenghao-ding@ti.com \
--cc=tiwai@suse.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
all inboxes | Powered by JetHome®