From: "Carlos O'Donell" <carlos@redhat.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Sodagudi Prasad <psodagud@codeaurora.org>,
linux-api@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: opaque types instead of union epoll_data
Date: Wed, 8 Mar 2017 12:34:07 -0500 [thread overview]
Message-ID: <ba7d0715-b59a-6596-9ec0-435999cd0e76@redhat.com> (raw)
In-Reply-To: <20170307175931.GA31000@kroah.com>
On 03/07/2017 12:59 PM, Greg KH wrote:
> On Tue, Mar 07, 2017 at 09:33:57AM -0500, Carlos O'Donell wrote:
>> I don't know anyone else who is working on this problem. Though I
>> have a vested interested in it as a glibc maintainer, since it would
>> be nice to avoid duplicate headers where possible between the kernel
>> and userspace.
>
> I've been working with the bionic developers to try to help clean up
> some of these things. Yes, epoll is messy here as you all have pointed
> out, and I'll be glad to review any patches that people submit for this.
> I need to get some spare time (hah!) to work through some of the issues
> that the bionic developers have already pointed out to me...
Sounds awesome. Please keep linux-api in the loop so the other libc
maintainers can follow along. From a glibc perspective I'm interested,
but also busy (see the other thread about libc-compat.h which has
immediate impact on header coordination).
--
Cheers,
Carlos.
next prev parent reply other threads:[~2017-03-08 17:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-07 12:31 opaque types instead of union epoll_data Sodagudi Prasad
2017-03-07 14:33 ` Carlos O'Donell
2017-03-07 17:59 ` Greg KH
2017-03-08 17:34 ` Carlos O'Donell [this message]
2017-03-08 18:01 ` Greg KH
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=ba7d0715-b59a-6596-9ec0-435999cd0e76@redhat.com \
--to=carlos@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=psodagud@codeaurora.org \
/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).