From: Corinna Vinschen <vinschen@redhat.com>
To: Jeff Johnston <jjohnstn@redhat.com>
Cc: joel@rtems.org, Newlib <newlib@sourceware.org>
Subject: Re: Adding aio.h and mqueue.h
Date: Fri, 2 Dec 2022 11:06:54 +0100 [thread overview]
Message-ID: <Y4nOPsQJ0FAFKuuQ@calimero.vinschen.de> (raw)
In-Reply-To: <CAOox84tokqMMW5mOgNN166bmttxmQiLmyGh=GQBjDhbTZuaADQ@mail.gmail.com>
On Dec 1 18:22, Jeff Johnston wrote:
> As long as the licensing is shared-newlib-compatible (non-GPL), it should
> be ok.
>
> -- Jeff J.
Cygwin already comes with aio.h and mqueue.h headers.
Ideally they are reused for newlib, or the new aio.h/mqueue.h headers
are checked that they provide the same definitions and replace the
Cygwin-only ones.
Thanks,
Corinna
>
> On Thu, Dec 1, 2022 at 11:37 AM Joel Sherrill <joel@rtems.org> wrote:
>
> > Hi
> >
> > We have migrated almost all of our POSIX defined header files from RTEMS
> > itself to newlib. I think aio.h and mqueue.h are the last POSIX headers
> > left on our side.
> >
> > What's the feeling on merging these? Would it be ok to put them in
> > newlib/libc/include?
> >
> > Our version of the headers have Doxygen comments. Would these be OK in
> > newlib or do I need to remove the Doxygen?
> >
> > Thanks.
> >
> > --joel
> >
> >
next prev parent reply other threads:[~2022-12-02 10:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-01 16:37 Joel Sherrill
2022-12-01 23:22 ` Jeff Johnston
2022-12-02 10:06 ` Corinna Vinschen [this message]
2022-12-02 14:15 ` Joel Sherrill
2022-12-02 17:10 ` Corinna Vinschen
2022-12-02 17:19 ` Joel Sherrill
2022-12-04 18:59 ` Corinna Vinschen
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=Y4nOPsQJ0FAFKuuQ@calimero.vinschen.de \
--to=vinschen@redhat.com \
--cc=jjohnstn@redhat.com \
--cc=joel@rtems.org \
--cc=newlib@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).