From: "Holalu Yogendra, Niranjan" <niranjan.hy@ti.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: "broonie@kernel.org" <broonie@kernel.org>,
"tiwai@suse.de" <tiwai@suse.de>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"Xu, Baojun" <baojun.xu@ti.com>,
"Ding, Shenghao" <shenghao-ding@ti.com>,
"liam.r.girdwood@intel.com" <liam.r.girdwood@intel.com>,
"Navada Kanyana, Mukund" <navada@ti.com>,
"Hampiholi, Vallabha" <v-hampiholi@ti.com>
Subject: Re: [PATCH v2 2/4] Asoc: tac5x1x: document tac5x1x codec
Date: Thu, 26 Jun 2025 14:23:43 +0000 [thread overview]
Message-ID: <02bd6e338b114622993ae829fb0d4f5b@ti.com> (raw)
Thank you for the time and review comment.
> From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> Sent: Wednesday, June 25, 2025 8:01 PM
> Subject: Re: [PATCH v2 2/4] Asoc: tac5x1x: document tac5x1x codec
>
> On Tue, Jun 24, 2025 at 09:07:40PM +0530, Niranjan H Y wrote:
> > tac5x1x family are series of low-power and high performance
> > mono/stereo audio codecs consists of ADC and DAC combinations.
>
> Aren't DT bindings changes supposed to follow the common template in the
> Subject?
Is it okay to change the subject in the next patch or keep using the
same subject tracking? please suggest.
>
> More important, the Cc list missed DT mailing lists and maintainers.
> What's going on here, please?
Pardon my ignorance.
I will address in the next patch.
Regards
Niranjan
next reply other threads:[~2025-06-27 13:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-26 14:23 Holalu Yogendra, Niranjan [this message]
2025-06-26 14:51 ` [PATCH v2 2/4] Asoc: tac5x1x: document tac5x1x codec Andy Shevchenko
-- strict thread matches above, loose matches on Subject: below --
2025-06-24 15:37 [PATCH v2 0/4] ASoc: tac5x1x: mixer-test report Niranjan H Y
2025-06-24 15:37 ` [PATCH v2 2/4] Asoc: tac5x1x: document tac5x1x codec Niranjan H Y
2025-06-25 14:30 ` Andy Shevchenko
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=02bd6e338b114622993ae829fb0d4f5b@ti.com \
--to=niranjan.hy@ti.com \
--cc=alsa-devel@alsa-project.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=baojun.xu@ti.com \
--cc=broonie@kernel.org \
--cc=liam.r.girdwood@intel.com \
--cc=navada@ti.com \
--cc=shenghao-ding@ti.com \
--cc=tiwai@suse.de \
--cc=v-hampiholi@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 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.