From: Takashi Iwai <tiwai@suse.de>
To: "Arvind Yadav" <arvind.yadav.cs@gmail.com>
Cc: <linux@armlinux.org.uk>, <clemens@ladisch.de>, <perex@perex.cz>,
<johannes@sipsolutions.net>, <daniel@zonque.org>,
<alsa-devel@alsa-project.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 00/13] constify alsa snd_pcm_ops structures
Date: Sat, 19 Aug 2017 11:04:31 +0200 [thread overview]
Message-ID: <s5hinhkszc0.wl-tiwai@suse.de> (raw)
In-Reply-To: <1503042321-26758-1-git-send-email-arvind.yadav.cs@gmail.com>
On Fri, 18 Aug 2017 09:45:08 +0200,
Arvind Yadav wrote:
>
> snd_pcm_ops are not supposed to change at runtime. All functions
> working with snd_pcm_ops provided by <sound/pcm.h> work with
> const snd_pcm_ops. So mark the non-const structs as const.
>
> Arvind Yadav (13):
> [PATCH 01/13] ALSA: aoa: constify snd_pcm_ops structures
> [PATCH 02/13] ALSA: arm: constify snd_pcm_ops structures
> [PATCH 03/13] ALSA: atmel: constify snd_pcm_ops structures
> [PATCH 04/13] ALSA: drivers: constify snd_pcm_ops structures
> [PATCH 05/13] ALSA: firewire: constify snd_pcm_ops structures
> [PATCH 06/13] ALSA: mips: constify snd_pcm_ops structures
> [PATCH 07/13] ALSA: parisc: constify snd_pcm_ops structures
> [PATCH 08/13] ALSA: pcmcia: constify snd_pcm_ops structures
> [PATCH 09/13] ALSA: ppc: constify snd_pcm_ops structures
> [PATCH 10/13] ALSA: sh: constify snd_pcm_ops structures
> [PATCH 11/13] ALSA: sparc: constify snd_pcm_ops structures
> [PATCH 12/13] ALSA: spi: constify snd_pcm_ops structures
> [PATCH 13/13] ALSA: usb: constify snd_pcm_ops structures
Applied all patches. Thanks.
Takashi
prev parent reply other threads:[~2017-08-19 9:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-18 7:45 Arvind Yadav
2017-08-18 7:45 ` [PATCH 01/13] ALSA: aoa: constify " Arvind Yadav
2017-08-18 7:45 ` [PATCH 02/13] ALSA: arm: " Arvind Yadav
2017-08-18 7:45 ` [PATCH 03/13] ALSA: atmel: " Arvind Yadav
2017-08-18 7:45 ` [PATCH 04/13] ALSA: drivers: " Arvind Yadav
2017-08-18 7:45 ` [PATCH 05/13] ALSA: firewire: " Arvind Yadav
2017-08-18 7:45 ` [PATCH 06/13] ALSA: mips: " Arvind Yadav
2017-08-18 7:45 ` [PATCH 07/13] ALSA: parisc: " Arvind Yadav
2017-08-18 7:45 ` [PATCH 08/13] ALSA: pcmcia: " Arvind Yadav
2017-08-18 7:45 ` [PATCH 13/13] ALSA: usb: " Arvind Yadav
2017-08-18 7:45 ` [PATCH 09/13] ALSA: ppc: " Arvind Yadav
2017-08-18 7:45 ` [PATCH 10/13] ALSA: sh: " Arvind Yadav
2017-08-18 7:45 ` [PATCH 11/13] ALSA: sparc: " Arvind Yadav
2017-08-18 7:45 ` [PATCH 12/13] ALSA: spi: " Arvind Yadav
2017-08-19 9:04 ` Takashi Iwai [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=s5hinhkszc0.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=arvind.yadav.cs@gmail.com \
--cc=clemens@ladisch.de \
--cc=daniel@zonque.org \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=perex@perex.cz \
/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®