From: "Xu, Baojun" <baojun.xu@ti.com>
To: Mark Brown <broonie@kernel.org>
Cc: "tiwai@suse.de" <tiwai@suse.de>,
"andriy.shevchenko@linux.intel.com"
<andriy.shevchenko@linux.intel.com>,
"13916275206@139.com" <13916275206@139.com>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"Ding, Shenghao" <shenghao-ding@ti.com>,
"linux-sound@vger.kernel.org" <linux-sound@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"lgirdwood@gmail.com" <lgirdwood@gmail.com>,
"robh@kernel.org" <robh@kernel.org>,
"krzk+dt@kernel.org" <krzk+dt@kernel.org>,
"conor+dt@kernel.org" <conor+dt@kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"Yi, Ken" <k-yi@ti.com>, "Lo, Henry" <henry.lo@ti.com>,
"Chen, Robin" <robinchen@ti.com>, "Ji, Jesse" <jesse-ji@ti.com>,
"Wang, Will" <will-wang@ti.com>,
"jim.shil@goertek.com" <jim.shil@goertek.com>,
"toastcheng@google.com" <toastcheng@google.com>,
"chinkaiting@google.com" <chinkaiting@google.com>
Subject: Re: [EXTERNAL] Re: [PATCH v4 1/2] ASoC: tas2781: Add tas2118, tas2x20, tas5825 support
Date: Mon, 8 Sep 2025 06:22:51 +0000 [thread overview]
Message-ID: <67fafc23d16d4790821321643a87385f@ti.com> (raw)
In-Reply-To: <b70314db-357f-4c39-a9b4-088d8ebed2b0@sirena.org.uk>
Hi Broonie,
> ________________________________________
> From: Mark Brown <broonie@kernel.org>
> Sent: 05 September 2025 18:41
> To: Xu, Baojun
> Cc: tiwai@suse.de; andriy.shevchenko@linux.intel.com; 13916275206@139.com; alsa-devel@alsa-project.org; Ding, Shenghao; linux-sound@vger.kernel.org; linux-kernel@vger.kernel.org; lgirdwood@gmail.com; robh@kernel.org; krzk+dt@kernel.org; conor+dt@kernel.org; devicetree@vger.kernel.org; Yi, Ken; Lo, Henry; Chen, Robin; Ji, Jesse; Wang, Will; jim.shil@goertek.com; toastcheng@google.com; chinkaiting@google.com
> Subject: Re: [EXTERNAL] Re: [PATCH v4 1/2] ASoC: tas2781: Add tas2118, tas2x20, tas5825 support
>
> On Fri, Sep 05, 2025 at 04:15:45AM +0000, Xu, Baojun wrote:
>
> > > This doesn't apply against current code, please check and resend.
>
> > Hi, do you mean I need a re-patch for the newest (next/linux-next.git) code?
> > Or need to create patches on tree broonie/linux.git?
>
> https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-6.18
>
This patch is also relative (shares the same include/sound/tas5825-tlv.h)
with another commit on next/linux-next.git:
https://patch.msgid.link/20250810122358.1575-1-baojun.xu@ti.com (ALSA: hda: Add TAS5825 support)
However, it was not merged into broonie/sound.git yet, should I wait for it?
Best Regards
Jim
next prev parent reply other threads:[~2025-09-08 6:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-30 6:14 [PATCH v4 1/2] ASoC: tas2781: Add tas2118, tas2x20, tas5825 support Baojun Xu
2025-08-30 6:14 ` [PATCH v4 2/2] " Baojun Xu
2025-09-02 20:52 ` Rob Herring (Arm)
2025-09-03 11:36 ` [PATCH v4 1/2] " Mark Brown
2025-09-05 4:15 ` [EXTERNAL] " Xu, Baojun
2025-09-05 10:41 ` Mark Brown
2025-09-08 6:22 ` Xu, Baojun [this message]
2025-09-08 17:10 ` Mark Brown
2025-09-09 6:43 ` Takashi Iwai
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=67fafc23d16d4790821321643a87385f@ti.com \
--to=baojun.xu@ti.com \
--cc=13916275206@139.com \
--cc=alsa-devel@alsa-project.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=broonie@kernel.org \
--cc=chinkaiting@google.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=henry.lo@ti.com \
--cc=jesse-ji@ti.com \
--cc=jim.shil@goertek.com \
--cc=k-yi@ti.com \
--cc=krzk+dt@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=robh@kernel.org \
--cc=robinchen@ti.com \
--cc=shenghao-ding@ti.com \
--cc=tiwai@suse.de \
--cc=toastcheng@google.com \
--cc=will-wang@ti.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