All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r@public.gmane.org>
To: Carlos O'Donell <carlos-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: Sodagudi Prasad
	<psodagud-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>,
	linux-api-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: opaque types instead of union epoll_data
Date: Wed, 8 Mar 2017 19:01:35 +0100	[thread overview]
Message-ID: <20170308180135.GA10747@kroah.com> (raw)
In-Reply-To: <ba7d0715-b59a-6596-9ec0-435999cd0e76-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>

On Wed, Mar 08, 2017 at 12:34:07PM -0500, Carlos O'Donell wrote:
> 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).

Ah, I forgot to cc: linux-api on my last epoll header file change, I'll
go do that now before I commit it to my tree for 4.12...

thanks,

greg k-h

WARNING: multiple messages have this Message-ID (diff)
From: Greg KH <gregkh@linuxfoundation.org>
To: "Carlos O'Donell" <carlos@redhat.com>
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 19:01:35 +0100	[thread overview]
Message-ID: <20170308180135.GA10747@kroah.com> (raw)
In-Reply-To: <ba7d0715-b59a-6596-9ec0-435999cd0e76@redhat.com>

On Wed, Mar 08, 2017 at 12:34:07PM -0500, Carlos O'Donell wrote:
> 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).

Ah, I forgot to cc: linux-api on my last epoll header file change, I'll
go do that now before I commit it to my tree for 4.12...

thanks,

greg k-h

  parent reply	other threads:[~2017-03-08 18:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-07 12:31 opaque types instead of union epoll_data Sodagudi Prasad
     [not found] ` <c06a9ceff1f2c8919ca81120de69f172-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2017-03-07 14:33   ` Carlos O'Donell
2017-03-07 14:33     ` Carlos O'Donell
2017-03-07 17:59     ` Greg KH
     [not found]       ` <20170307175931.GA31000-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>
2017-03-08 17:34         ` Carlos O'Donell
2017-03-08 17:34           ` Carlos O'Donell
     [not found]           ` <ba7d0715-b59a-6596-9ec0-435999cd0e76-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2017-03-08 18:01             ` Greg KH [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=20170308180135.GA10747@kroah.com \
    --to=gregkh-hqyy1w1ycw8ekmwlsbkhg0b+6bgklq7r@public.gmane.org \
    --cc=carlos-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
    --cc=linux-api-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=psodagud-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.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 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.