From: "Xu, Baojun" <baojun.xu@ti.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: "broonie@kernel.org" <broonie@kernel.org>,
"andriy.shevchenko@linux.intel.com"
<andriy.shevchenko@linux.intel.com>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"Ding, Shenghao" <shenghao-ding@ti.com>,
"Navada Kanyana, Mukund" <navada@ti.com>,
"13916275206@139.com" <13916275206@139.com>,
"Hampiholi, Vallabha" <v-hampiholi@ti.com>,
"P O, Vijeth" <v-po@ti.com>,
"linux-sound@vger.kernel.org" <linux-sound@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [EXTERNAL] Re: [PATCH v1] ALSA: hda: Add TAS2770 support
Date: Sat, 19 Jul 2025 04:29:52 +0000 [thread overview]
Message-ID: <26bbebb22e0046bcb154dcfd5c7094e9@ti.com> (raw)
In-Reply-To: <87ms917kdl.wl-tiwai@suse.de>
>
> ________________________________________
> From: Takashi Iwai <tiwai@suse.de>
> Sent: 18 July 2025 20:29
> To: Xu, Baojun
> Cc: broonie@kernel.org; andriy.shevchenko@linux.intel.com; alsa-devel@alsa-project.org; Ding, Shenghao; Navada Kanyana, Mukund; 13916275206@139.com; Hampiholi, Vallabha; P O, Vijeth; linux-sound@vger.kernel.org; linux-kernel@vger.kernel.org
> Subject: [EXTERNAL] Re: [PATCH v1] ALSA: hda: Add TAS2770 support
>
> On Fri, 18 Jul 2025 11: 44: 54 +0200, Baojun Xu wrote:
>
> Add TAS2770 support in TI's HDA driver.
> And add hda_chip_id for more product support in the future.
> Separated DSP and non-DSP in firmware load function.
>
> Signed-off-by:
> ZjQcmQRYFpfptBannerStart
> This message was sent from outside of Texas Instruments.
> Do not click links or open attachments unless you recognize the source of this email and know the content is safe.
> <https://us-phishalarm-ewt.proofpoint.com/EWT/v1/G3vK!vxdrHfwnF007wWzvvxtoX6USmVeMCYVcebtNTsaFw2PGCzl2HC8-5XErXla_Mkw92m8ysw$>
> Report Suspicious
>
> ZjQcmQRYFpfptBannerEnd
>
> On Fri, 18 Jul 2025 11:44:54 +0200,
> Baojun Xu wrote:
> >
> > Add TAS2770 support in TI's HDA driver.
> > And add hda_chip_id for more product support in the future.
> > Separated DSP and non-DSP in firmware load function.
> >
> > Signed-off-by: Baojun Xu <baojun.xu@ti.com>
>
> Any reason of the submission of the very same patch?
> It was requested to resubmit after rebasing to the new location for
> HD-audio (sound/hda/*) as found in for-next branch of sound.git tree.
>
I have uploaded to:
git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git,
and you said:
"Takashi Iwai <tiwai@suse.de>, Sat 12/07/2025 16:29
The whole HD-audio stuff has been moved under sound/hda recently.
Please create a patch based on for-next branch of the sound git tree."
So I re-patched it to for-next:
git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.
Do I have a misunderstanding about it? Do I still need patch on
/next/linux-next.git, just after the code was moved to sound/hda/codecs/side-codecs?
>
> thanks,
>
> Takashi
>
Best Regards
Jim
prev parent reply other threads:[~2025-07-24 16:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-18 9:44 [PATCH v1] ALSA: hda: Add TAS2770 support Baojun Xu
2025-07-18 12:29 ` Takashi Iwai
2025-07-19 4:29 ` Xu, Baojun [this message]
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=26bbebb22e0046bcb154dcfd5c7094e9@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=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=navada@ti.com \
--cc=shenghao-ding@ti.com \
--cc=tiwai@suse.de \
--cc=v-hampiholi@ti.com \
--cc=v-po@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;
as well as URLs for NNTP newsgroup(s).