From: Jaroslav Kysela <perex@perex.cz>
To: alsa-devel@alsa-project.org
Cc: Takashi Iwai <tiwai@suse.de>
Subject: Re: [PATCH 0/8] Proc file cleanups
Date: Thu, 23 Apr 2015 17:03:47 +0200 [thread overview]
Message-ID: <553909D3.5030201@perex.cz> (raw)
In-Reply-To: <1429800570-10153-1-git-send-email-tiwai@suse.de>
Dne 23.4.2015 v 16:49 Takashi Iwai napsal(a):
> Hi,
>
> here is a series of patches for cleaning up the ALSA proc file
> management code. The biggest change is the use of seq_file for text
> reads, but all are internal and the API is kept intact.
>
> The rest are mostly small cleanups and refactoring.
>
> The patches are found in topic/proc branch of sound git tree.
The changes look good.
Acked-by: Jaroslav Kysela <perex@perex.cz>
--
Jaroslav Kysela <perex@perex.cz>
Linux Kernel Sound Maintainer
ALSA Project; Red Hat, Inc.
prev parent reply other threads:[~2015-04-23 15:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-23 14:49 [PATCH 0/8] Proc file cleanups Takashi Iwai
2015-04-23 14:49 ` [PATCH 1/8] ALSA: core: Use seq_file for text proc file reads Takashi Iwai
2015-04-23 14:49 ` [PATCH 2/8] ALSA: core: Fix possible memory leaks at error path in info.c Takashi Iwai
2015-04-23 14:49 ` [PATCH 3/8] ALSA: core: Remove child proc file elements recursively Takashi Iwai
2015-04-23 14:49 ` [PATCH 4/8] ALSA: core: Manage asound root directory with snd_info_entry Takashi Iwai
2015-04-23 14:49 ` [PATCH 5/8] ALSA: core: Remove superfluous exit calls for proc entries Takashi Iwai
2015-04-23 14:49 ` [PATCH 6/8] ALSA: core: Don't ignore errors at creating proc files Takashi Iwai
2015-04-23 14:49 ` [PATCH 7/8] ALSA: core: Build conditionally and remove superfluous ifdefs Takashi Iwai
2015-04-23 14:49 ` [PATCH 8/8] ALSA: core: Clean up OSS proc file management Takashi Iwai
2015-04-23 15:03 ` Jaroslav Kysela [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=553909D3.5030201@perex.cz \
--to=perex@perex.cz \
--cc=alsa-devel@alsa-project.org \
--cc=tiwai@suse.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.