From: Markus Elfring <Markus.Elfring@web.de>
To: Zhu Jun <zhujun2@cmss.chinamobile.com>,
linux-sound@vger.kernel.org, Jaroslav Kysela <perex@perex.cz>,
Takashi Iwai <tiwai@suse.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
"Andy Shevchenko" <andriy.shevchenko@linux.intel.com>,
"Heiko Stübner" <heiko@sntech.de>,
"Kuninori Morimoto" <kuninori.morimoto.gx@renesas.com>,
"Liam Girdwood" <lgirdwood@gmail.com>,
"Mark Brown" <broonie@kernel.org>,
"Nathan Chancellor" <nathan@kernel.org>,
"Uwe Kleine-König" <u.kleine-koenig@baylibre.com>,
"Weidong Wang" <wangweidong.a@awinic.com>
Subject: Re: [PATCH v3?] ASoC: codecs: aw88399: Fix error handling in aw_dev_get_dsp_status()
Date: Wed, 9 Oct 2024 13:12:21 +0200 [thread overview]
Message-ID: <fbbe290b-4dd4-4a65-acfb-8150b621a5c7@web.de> (raw)
In-Reply-To: <20241009094313.8820-1-zhujun2@cmss.chinamobile.com>
> Changed the error handling in aw_dev_get_dsp_status to return -EPERM directly
> instead of setting it to a variable.
* How do you think about to choose an imperative wording for an improved change description?
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?h=v6.12-rc2#n94
* Would you like to add any tags (like “Fixes” and “Cc”) accordingly?
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?h=v6.12-rc2#n145
…
> ---
> V1 -> V2:
> - add a dot after the commit
> - modify commit info
Can it be that higher version numbers would be more appropriate according to
the evolving patch review?
Regards,
Markus
next prev parent reply other threads:[~2024-10-09 11:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-09 9:43 [PATCH v2] ASoC: codecs: Fix error handling in aw_dev_get_dsp_status() Zhu Jun
2024-10-09 11:12 ` Markus Elfring [this message]
2024-10-09 12:47 ` [PATCH v3?] ASoC: codecs: aw88399: " 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=fbbe290b-4dd4-4a65-acfb-8150b621a5c7@web.de \
--to=markus.elfring@web.de \
--cc=andriy.shevchenko@linux.intel.com \
--cc=broonie@kernel.org \
--cc=heiko@sntech.de \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=nathan@kernel.org \
--cc=perex@perex.cz \
--cc=tiwai@suse.com \
--cc=u.kleine-koenig@baylibre.com \
--cc=wangweidong.a@awinic.com \
--cc=zhujun2@cmss.chinamobile.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