From: "Lu, Kevin" <kevin-lu@ti.com>
To: Mark Brown <broonie@kernel.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Ding, Shenghao" <shenghao-ding@ti.com>,
"Lu, Kevin" <kevin-lu@ti.com>,
"Navada Kanyana, Mukund" <navada@ti.com>
Subject: RE: [EXTERNAL] Re: [PATCH v1 1/1] sound: Add a new kcontrol
Date: Wed, 17 Aug 2022 00:30:58 +0000 [thread overview]
Message-ID: <37c2d0db2f4240fe80ff43504a31ebcd@ti.com> (raw)
In-Reply-To: <YvvYbkDSodLBkD0R@sirena.org.uk>
Hi Mark,
Thanks for your patience to point out my mistakes, It will be helpful for the future patch submitting.
I will take every code change carefully.
Best regards
Kevin
-----Original Message-----
From: Mark Brown <broonie@kernel.org>
Sent: Wednesday, August 17, 2022 1:49 AM
To: Kevin Lu <luminlong@139.com>
Cc: linux-kernel@vger.kernel.org; Ding, Shenghao <shenghao-ding@ti.com>; Lu, Kevin <kevin-lu@ti.com>
Subject: [EXTERNAL] Re: [PATCH v1 1/1] sound: Add a new kcontrol
On Mon, Aug 15, 2022 at 07:27:15PM +0800, Kevin Lu wrote:
> Add a new kcontrol for phase calib
This looks mostly good now - one small issue below which I'll fix up myself and apply.
Please submit patches using subject lines reflecting the style for the subsystem, this makes it easier for people to identify relevant patches.
Look at what existing commits in the area you're changing are doing and make sure your subject lines visually resemble what they're doing.
There's no need to resubmit to fix this alone.
> + ADCX140_PHASE_CALIB_SWITCH("Adcx140 Phase Calib Switch"),
We wouldn't normally put the CODEC name in the control name, it's not really relevant to users and if some disambiguation is needed it's usually better to do it in a board specific way (eg, describing the output the CODEC is connected to) using the support ASoC has for adding prefixes. Better would be "Phase Callibration Switch".
next prev parent reply other threads:[~2022-08-17 0:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-15 11:27 [PATCH v1 1/1] sound: Add a new kcontrol Kevin Lu
2022-08-16 17:48 ` Mark Brown
2022-08-17 0:30 ` Lu, Kevin [this message]
2022-08-17 14:31 ` 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=37c2d0db2f4240fe80ff43504a31ebcd@ti.com \
--to=kevin-lu@ti.com \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=navada@ti.com \
--cc=shenghao-ding@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