From: Ilias Izmaylov <ikizmaylov@salutedevices.com>
To: Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>, Jaroslav Kysela <perex@perex.cz>,
Takashi Iwai <tiwai@suse.com>,
Igor Prusov <ivprusov@salutedevices.com>,
Chen Ni <nichen@iscas.ac.cn>
Cc: <kernel@salutedevices.com>, <linux-sound@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <rulkc@linuxtesting.org>
Subject: Re: [PATCH v1 0/2] Fix snd_soc_component_update_bits return handling
Date: Thu, 12 Feb 2026 12:39:20 +0300 [thread overview]
Message-ID: <e7ef697d-b7db-47ed-b622-4cac026174e0@salutedevices.com> (raw)
In-Reply-To: <20260120161200.3590305-1-ikizmaylov@salutedevices.com>
Hey!
I noticed that it's been more than two weeks since I submitted this patch series and there is still no reply so I decided to ping you guys just in case
On 1/20/26 19:11, Ilias Izmaylov wrote:
> This patchset fixes the way that snd_soc_component_update_bits
> function's return values are handled by codecs ntp8918 and ntp8835.
>
> Currently the return value "0" is considered erroneous when in fact it
> isn't and what would correctly indicate an error is a negative return
> value.
>
> Ilias Izmaylov (2):
> ASoC: codecs: ntp8918: fix snd_soc_component_update_bits handling
> ASoC: codecs: ntp8835: fix snd_soc_component_update_bits handling
>
> sound/soc/codecs/ntp8835.c | 17 ++++++++++++-----
> sound/soc/codecs/ntp8918.c | 17 ++++++++++++-----
> 2 files changed, 24 insertions(+), 10 deletions(-)
>
prev parent reply other threads:[~2026-02-12 9:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-20 16:11 Ilias Izmaylov
2026-01-20 16:11 ` [PATCH v1 1/2] ASoC: codecs: ntp8918: fix snd_soc_component_update_bits handling Ilias Izmaylov
2026-01-20 16:11 ` [PATCH v1 2/2] ASoC: codecs: ntp8835: " Ilias Izmaylov
2026-02-12 8:08 ` [PATCH v1 0/2] Fix snd_soc_component_update_bits return handling Ilias Izmaylov
2026-02-12 9:39 ` Ilias Izmaylov [this message]
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=e7ef697d-b7db-47ed-b622-4cac026174e0@salutedevices.com \
--to=ikizmaylov@salutedevices.com \
--cc=broonie@kernel.org \
--cc=ivprusov@salutedevices.com \
--cc=kernel@salutedevices.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=nichen@iscas.ac.cn \
--cc=perex@perex.cz \
--cc=rulkc@linuxtesting.org \
--cc=tiwai@suse.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
all inboxes | Powered by JetHome®