From: Takashi Iwai <tiwai@suse.de>
To: "Kees Cook" <keescook@chromium.org>
Cc: <linux-kernel@vger.kernel.org>, <alsa-devel@alsa-project.org>,
"Jaroslav Kysela" <perex@perex.cz>
Subject: Re: [PATCH] ALSA: use designated initializers
Date: Wed, 28 Dec 2016 16:06:38 +0100 [thread overview]
Message-ID: <s5hwpekum81.wl-tiwai@suse.de> (raw)
In-Reply-To: <20161217005944.GA140281@beast>
On Sat, 17 Dec 2016 01:59:44 +0100,
Kees Cook wrote:
>
> Prepare to mark sensitive kernel structures for randomization by making
> sure they're using designated initializers. These were identified during
> allyesconfig builds of x86, arm, and arm64, with most initializer fixes
> extracted from grsecurity.
>
> Signed-off-by: Kees Cook <keescook@chromium.org>
Applied, thanks.
Takashi
> ---
> sound/synth/emux/emux_seq.c | 14 +++++++-------
> 1 file changed, 7 insertions(+), 7 deletions(-)
>
> diff --git a/sound/synth/emux/emux_seq.c b/sound/synth/emux/emux_seq.c
> index a0209204ae48..55579f6b8cb2 100644
> --- a/sound/synth/emux/emux_seq.c
> +++ b/sound/synth/emux/emux_seq.c
> @@ -33,13 +33,13 @@ static int snd_emux_unuse(void *private_data, struct snd_seq_port_subscribe *inf
> * MIDI emulation operators
> */
> static struct snd_midi_op emux_ops = {
> - snd_emux_note_on,
> - snd_emux_note_off,
> - snd_emux_key_press,
> - snd_emux_terminate_note,
> - snd_emux_control,
> - snd_emux_nrpn,
> - snd_emux_sysex,
> + .note_on = snd_emux_note_on,
> + .note_off = snd_emux_note_off,
> + .key_press = snd_emux_key_press,
> + .note_terminate = snd_emux_terminate_note,
> + .control = snd_emux_control,
> + .nrpn = snd_emux_nrpn,
> + .sysex = snd_emux_sysex,
> };
>
>
> --
> 2.7.4
>
>
> --
> Kees Cook
> Nexus Security
>
prev parent reply other threads:[~2016-12-28 15:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-17 0:59 [PATCH] ALSA: use designated initializers Kees Cook
2016-12-17 10:17 ` Takashi Sakamoto
2016-12-28 15:06 ` 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=s5hwpekum81.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--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