From: Kevin Lu <luminlong@139.com>
To: broonie@kernel.org
Cc: linux-kernel@vger.kernel.org, shenghao-ding@ti.com,
kevin-lu@ti.com, Kevin Lu <luminlong@139.com>
Subject: [PATCH v1 0/1]
Date: Mon, 1 Aug 2022 10:59:38 +0800 [thread overview]
Message-ID: <20220801025939.2343-1-luminlong@139.com> (raw)
*** BLURB HERE ***
Kevin Lu (1):
Add a new kcontrol for phase calib, remove unnecessary header file,
make code more comply with linux coding style
--
2.17.1
next reply other threads:[~2022-08-01 3:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-01 2:59 Kevin Lu [this message]
2022-08-01 2:59 ` [PATCH v1 1/1] Add a new kcontrol for phase calib, remove unnecessary header file, make code more comply with linux coding style Kevin Lu
2022-08-01 13:14 ` Mark Brown
2022-08-01 11:15 ` [PATCH v1 0/1] Mark Brown
-- strict thread matches above, loose matches on Subject: below --
2022-08-07 3:40 Kevin Lu
2022-08-08 11:35 ` 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=20220801025939.2343-1-luminlong@139.com \
--to=luminlong@139.com \
--cc=broonie@kernel.org \
--cc=kevin-lu@ti.com \
--cc=linux-kernel@vger.kernel.org \
--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