From: Willem de Bruijn <willemdebruijn.kernel@gmail.com>
To: netdev@vger.kernel.org
Cc: davem@davemloft.net, linux-kernel@vger.kernel.org,
john.stultz@linaro.rg, bmoses@google.com,
Willem de Bruijn <willemb@google.com>
Subject: [PATCH net-next 0/2] uapi: include time.h from errqueue.h
Date: Mon, 12 Sep 2016 13:05:28 -0400 [thread overview]
Message-ID: <1473699930-58865-1-git-send-email-willemdebruijn.kernel@gmail.com> (raw)
From: Willem de Bruijn <willemb@google.com>
It was reported that linux/errqueue.h requires linux/time.h, but that
adding the include directly may cause userspace conflicts between
linux/time.h and glibc time.h:
https://lkml.org/lkml/2016/7/10/10
Address the conflicts using the standard libc-compat approach, then
add the #include to errqueue.h
The first patch is a resubmit. It was previously submitted to
tip/timers/core, but given the commit history, the maintainer
suggested this tree, instead.
https://lkml.org/lkml/2016/8/10/748
This also allows sending the follow-up as part of the patchset.
Willem de Bruijn (2):
uapi glibc compat: make linux/time.h compile with user time.h files
errqueue: include linux/time.h
include/uapi/linux/errqueue.h | 1 +
include/uapi/linux/libc-compat.h | 50 ++++++++++++++++++++++++++++++++++++++++
include/uapi/linux/time.h | 15 ++++++++++++
3 files changed, 66 insertions(+)
--
2.8.0.rc3.226.g39d4020
next reply other threads:[~2016-09-12 17:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-12 17:05 Willem de Bruijn [this message]
2016-09-12 17:05 ` [PATCH net-next 1/2] uapi glibc compat: make linux/time.h compile with user time.h files Willem de Bruijn
2016-09-12 17:05 ` [PATCH net-next 2/2] errqueue: include linux/time.h Willem de Bruijn
2016-09-12 19:26 ` kbuild test robot
2016-09-12 20:09 ` Willem de Bruijn
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=1473699930-58865-1-git-send-email-willemdebruijn.kernel@gmail.com \
--to=willemdebruijn.kernel@gmail.com \
--cc=bmoses@google.com \
--cc=davem@davemloft.net \
--cc=john.stultz@linaro.rg \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=willemb@google.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;
as well as URLs for NNTP newsgroup(s).