From: Takashi Iwai <tiwai@suse.de>
To: "Dmitry V. Levin" <ldv@altlinux.org>
Cc: Jorge Sanjuan <jorge.sanjuan@codethink.co.uk>,
Ruslan Bilovol <ruslan.bilovol@gmail.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] uapi: fix linux/usb/audio.h userspace compilation error
Date: Mon, 13 Aug 2018 18:09:46 +0200 [thread overview]
Message-ID: <s5h8t5afdth.wl-tiwai@suse.de> (raw)
In-Reply-To: <20180813160106.GA22902@altlinux.org>
On Mon, 13 Aug 2018 18:01:06 +0200,
Dmitry V. Levin wrote:
>
> On Mon, Aug 13, 2018 at 05:55:25PM +0200, Takashi Iwai wrote:
> > On Mon, 13 Aug 2018 17:46:51 +0200, Dmitry V. Levin wrote:
> > >
> > > Replace NULL with 0 in uac_mixer_unit_bmControls() to fix the following
> > > linux/usb/audio.h userspace compilation error:
> > >
> > > /usr/include/linux/usb/audio.h: In function 'uac_mixer_unit_bmControls':
> > > /usr/include/linux/usb/audio.h:304:10: error: 'NULL' undeclared (first use in this function)
> > > return NULL;
> > >
> > > Fixes: 6cfd839ae78e ("ALSA: usb-audio: UAC3. Add support for mixer unit.")
> > > Cc: <stable@vger.kernel.org> # v4.18
> > > Signed-off-by: Dmitry V. Levin <ldv@altlinux.org>
> >
> > Hrm, can we include the standard header for definition of NULL
> > instead? It's way too ugly to use 0 just for that.
>
> It's fine to return 0 as a null pointer.
Fine from syntax POV, but not from semantic.
> If you prefer NULL,
> please include a header that won't break userspace,
> or just move the function out of UAPI.
Maybe better to remove the function from uapi, then.
Takashi
prev parent reply other threads:[~2018-08-13 16:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-13 15:46 [PATCH] uapi: fix linux/usb/audio.h userspace compilation error Dmitry V. Levin
2018-08-13 15:55 ` Takashi Iwai
2018-08-13 16:01 ` Dmitry V. Levin
2018-08-13 16:09 ` 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=s5h8t5afdth.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=gregkh@linuxfoundation.org \
--cc=jorge.sanjuan@codethink.co.uk \
--cc=ldv@altlinux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ruslan.bilovol@gmail.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