[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <fbd5666c-f681-4f09-eb5c-35c47d60d857@web.de>
Date: Sun, 14 Jul 2019 12:07:18 +0200
From: Markus Elfring <Markus.Elfring@....de>
To: Wen Yang <wen.yang99@....com.cn>, alsa-devel@...a-project.org
Cc: Cheng Shengyu <cheng.shengyu@....com.cn>,
Jaroslav Kysela <perex@...ex.cz>,
Krzysztof Kozlowski <krzk@...nel.org>,
Liam Girdwood <lgirdwood@...il.com>,
Mark Brown <broonie@...nel.org>,
Sangbeom Kim <sbkim73@...sung.com>,
Sylwester Nawrocki <s.nawrocki@...sung.com>,
Takashi Iwai <tiwai@...e.com>,
Xue Zhihong <xue.zhihong@....com.cn>,
Yi Wang <wang.yi59@....com.cn>,
LKML <linux-kernel@...r.kernel.org>,
kernel-janitors@...r.kernel.org
Subject: Re: [PATCH 0/2] ASoC: samsung: odroid: fix err handling of
odroid_audio_probe
Would a subject like “ASoC: samsung: odroid: Fix handling of device node references
in odroid_audio_probe” be more appropriate (instead of using the abbreviation “err”)?
> We developed a coccinelle SmPL to detect …
* I would find a slightly different wording better.
* How do you think about to convert this information into software attributions
for the update steps?
Regards,
Markus
Powered by blists - more mailing lists