From: Greg KH <gregkh@linuxfoundation.org>
To: David Howells <dhowells@redhat.com>
Cc: mchehab@s-opensource.com, apw@canonical.com, joe@perches.com,
hans.verkuil@cisco.com,
ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] UAPI headers and inline function policy
Date: Mon, 23 Jan 2017 12:35:27 +0100 [thread overview]
Message-ID: <20170123113527.GB31821@kroah.com> (raw)
In-Reply-To: <31831.1485170425@warthog.procyon.org.uk>
On Mon, Jan 23, 2017 at 11:20:25AM +0000, David Howells wrote:
> I noticed that include/uapi/linux/cec.h and cec-funcs.h export a bunch of
> inline functions to userspace. I think that the following should possibly be
> prohibited in kernel UAPI headers:
>
> (1) Inline functions and function declarations.
As the lustre filesystem wants to do the same thing that cec is doing,
where would the best place be to put stuff like this that would
otherwise just require two independant copies to be kept in sync?
thanks,
greg k-h
next prev parent reply other threads:[~2017-01-23 11:35 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 [this message]
2017-01-23 17:27 ` David Howells
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=20170123113527.GB31821@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=apw@canonical.com \
--cc=dhowells@redhat.com \
--cc=hans.verkuil@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