From: SF Markus Elfring <elfring@users.sourceforge.net>
To: alsa-devel@alsa-project.org, Bhumika Goyal <bhumirks@gmail.com>,
David Howells <dhowells@redhat.com>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>
Cc: kernel-janitors@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: [PATCH 0/4] ALSA-Riptide: Fine-tuning for seven function implementations
Date: Fri, 17 Nov 2017 10:46:10 +0100 [thread overview]
Message-ID: <0eef2699-f28a-c1e0-9351-268b5eb7e0c1@users.sourceforge.net> (raw)
From: Markus Elfring <elfring@users.sourceforge.net>
Date: Fri, 17 Nov 2017 10:32:23 +0100
A few update suggestions were taken into account
from static source code analysis.
Markus Elfring (4):
Adjust 13 function calls together with a variable assignment
Delete an unnecessary variable initialisation in snd_riptide_proc_read()
Reduce the scope for two variables in snd_riptide_proc_read()
Use common error handling code in snd_riptide_create()
sound/pci/riptide/riptide.c | 78 ++++++++++++++++++++++++++-------------------
1 file changed, 46 insertions(+), 32 deletions(-)
--
2.15.0
next reply other threads:[~2017-11-17 9:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-17 9:46 SF Markus Elfring [this message]
2017-11-17 9:47 ` [PATCH 1/4] ALSA: riptide: Adjust 13 function calls together with a variable assignment SF Markus Elfring
2017-11-17 9:49 ` [PATCH 2/4] ALSA: riptide: Delete an unnecessary variable initialisation in snd_riptide_proc_read() SF Markus Elfring
2017-11-17 9:50 ` [PATCH 3/4] ALSA: riptide: Reduce the scope for two variables " SF Markus Elfring
2017-11-17 9:51 ` [PATCH 4/4] ALSA: riptide: Use common error handling code in snd_riptide_create() SF Markus Elfring
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=0eef2699-f28a-c1e0-9351-268b5eb7e0c1@users.sourceforge.net \
--to=elfring@users.sourceforge.net \
--cc=alsa-devel@alsa-project.org \
--cc=bhumirks@gmail.com \
--cc=dhowells@redhat.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--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;
as well as URLs for NNTP newsgroup(s).