From: David Howells <dhowells@redhat.com>
To: Hans Verkuil <hansverk@cisco.com>
Cc: mchehab@s-opensource.com,
ksummit-discuss@lists.linuxfoundation.org, apw@canonical.com,
hans.verkuil@cisco.com, joe@perches.com
Subject: Re: [Ksummit-discuss] UAPI headers and inline function policy
Date: Mon, 23 Jan 2017 17:27:32 +0000 [thread overview]
Message-ID: <3109.1485192452@warthog.procyon.org.uk> (raw)
In-Reply-To: <521f636c-c768-2d01-18c6-e5b6b96b6d8f@cisco.com>
Hans Verkuil <hansverk@cisco.com> wrote:
> > (1) Inline functions and function declarations.
>
> The reason for putting them there is that these inline functions are used
> both in the kernel and in userspace. Having them in one place makes life
> much simpler.
>
> What is the rationale for not allowing this?
>
> > (2) Anonymous embedded structs and unions.
>
> Same question. Anonymous unions are used in many places and have been for
> many years. Certainly in the media subsystem they are used frequently.
Not all compilers support these features. Also, we have to be very careful
about using reserved words like "new" in parameter and variable names.
David
prev parent reply other threads:[~2017-01-23 17:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <521f636c-c768-2d01-18c6-e5b6b96b6d8f@cisco.com>
2017-01-23 11:20 ` David Howells
2017-01-23 11:35 ` Greg KH
2017-01-23 17:27 ` David Howells [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=3109.1485192452@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=apw@canonical.com \
--cc=hans.verkuil@cisco.com \
--cc=hansverk@cisco.com \
--cc=joe@perches.com \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=mchehab@s-opensource.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