From: Takashi Iwai <tiwai@suse.de>
To: alsa-devel@alsa-project.org
Subject: [alsa-devel] [PATCH 0/5] ALSA: Fix uapi headers
Date: Fri, 20 Dec 2019 16:34:10 +0100 [thread overview]
Message-ID: <20191220153415.2740-1-tiwai@suse.de> (raw)
Hi,
here is a series of fixes for include/uapi/sound/*.h files and the
relevant code changes, so that they can be used for building
alsa-tools programs again.
The corresponding alsa-lib update will be followed.
Takashi
===
Takashi Iwai (5):
ALSA: emu10k1: Make uapi/emu10k1.h compilable again
ALSA: hdsp: Make uapi/hdsp.h compilable again
ALSA: hdspm: Drop linux/types.h inclusion in uapi header
ALSA: uapi: Fix typos and header inclusion in asound.h
ALSA: uapi: Drop asound.h inclusion from asoc.h
include/uapi/sound/asoc.h | 1 -
include/uapi/sound/asound.h | 6 +++---
include/uapi/sound/emu10k1.h | 38 ++++++++++++++++++++++++++------------
include/uapi/sound/hdsp.h | 4 +---
include/uapi/sound/hdspm.h | 2 --
sound/pci/emu10k1/emufx.c | 26 ++++++++++++++------------
sound/pci/rme9652/hdsp.c | 2 +-
7 files changed, 45 insertions(+), 34 deletions(-)
--
2.16.4
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
https://mailman.alsa-project.org/mailman/listinfo/alsa-devel
next reply other threads:[~2019-12-20 15:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-20 15:34 Takashi Iwai [this message]
2019-12-20 15:34 ` [alsa-devel] [PATCH 1/5] ALSA: emu10k1: Make uapi/emu10k1.h compilable again Takashi Iwai
2019-12-20 15:34 ` [alsa-devel] [PATCH 2/5] ALSA: hdsp: Make uapi/hdsp.h " Takashi Iwai
2019-12-20 15:34 ` [alsa-devel] [PATCH 3/5] ALSA: hdspm: Drop linux/types.h inclusion in uapi header Takashi Iwai
2019-12-20 15:34 ` [alsa-devel] [PATCH 4/5] ALSA: uapi: Fix typos and header inclusion in asound.h Takashi Iwai
2019-12-20 15:34 ` [alsa-devel] [PATCH 5/5] ALSA: uapi: Drop asound.h inclusion from asoc.h Takashi Iwai
2020-03-30 16:53 ` Dmitry V. Levin
2020-03-30 19:11 ` Takashi Iwai
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=20191220153415.2740-1-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
/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