From: Arnd Bergmann <arnd@arndb.de>
To: Gabriel Laskar <gabriel@lse.epita.fr>
Cc: Thomas Gleixner <tglx@linutronix.de>,
"David S. Miller" <davem@davemloft.net>,
Hans Verkuil <hans.verkuil@cisco.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Mauro Carvalho Chehab <mchehab@osg.samsung.com>,
stephen hemminger <stephen@networkplumber.org>,
Nicolas Dichtel <nicolas.dichtel@6wind.com>,
Masahiro Yamada <yamada.m@jp.panasonic.com>,
open list <linux-kernel@vger.kernel.org>,
"open list:ABI/API" <linux-api@vger.kernel.org>
Subject: Re: [PATCH] timerfd: expose uapi header
Date: Mon, 05 Oct 2015 16:57:21 +0200 [thread overview]
Message-ID: <5414742.dPp9ExW9xv@wuerfel> (raw)
In-Reply-To: <1444056829-9118-1-git-send-email-gabriel@lse.epita.fr>
On Monday 05 October 2015 16:53:39 Gabriel Laskar wrote:
> this patch expose the timerfd apis to the userland. It is already in
> glibc header sys/timerfd.h but not synchronised, and missing the ioctl
> number definition.
>
> Signed-off-by: Gabriel Laskar <gabriel@lse.epita.fr>
>
What happens if you include both sys/timerfd.h and linux/timerfd.h then?
> header-y += telephony.h
> header-y += termios.h
> header-y += thermal.h
>+header-y += tiemrfd.h
> header-y += time.h
> header-y += times.h
> header-y += timex.h
s/tiemrfd/timerfd/
Arnd
next prev parent reply other threads:[~2015-10-05 14:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-05 14:53 [PATCH] timerfd: expose uapi header Gabriel Laskar
2015-10-05 14:53 ` Gabriel Laskar
2015-10-05 14:57 ` Arnd Bergmann [this message]
2015-10-05 19:20 ` Gabriel Laskar
2015-10-05 19:20 ` Gabriel Laskar
[not found] ` <1444056829-9118-1-git-send-email-gabriel-tU7rkvAWjlwhT4uAktR2oQ@public.gmane.org>
2015-10-05 14:57 ` Yann Droneaud
2015-10-05 14:57 ` Yann Droneaud
2015-10-05 15:02 ` kbuild test robot
2015-10-05 15:02 ` kbuild test robot
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=5414742.dPp9ExW9xv@wuerfel \
--to=arnd@arndb.de \
--cc=davem@davemloft.net \
--cc=gabriel@lse.epita.fr \
--cc=gregkh@linuxfoundation.org \
--cc=hans.verkuil@cisco.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@osg.samsung.com \
--cc=mst@redhat.com \
--cc=nicolas.dichtel@6wind.com \
--cc=stephen@networkplumber.org \
--cc=tglx@linutronix.de \
--cc=yamada.m@jp.panasonic.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.