From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/uclibc: Add eventfd_read() and eventfd_write()
Date: Mon, 8 Dec 2014 23:25:47 +0100 [thread overview]
Message-ID: <20141208222547.GE4105@free.fr> (raw)
In-Reply-To: <1414183436-6964-1-git-send-email-bernd.kuhls@t-online.de>
Bernd, All,
On 2014-10-24 22:43 +0200, Bernd Kuhls spake thusly:
> Needed for upcoming eventfd support in Kodi:
> https://github.com/FernetMenta/xbmc/commit/1030119691a67511b6e9a27abdec474525de8d26
As Peter said, we do not like to carry feature patches in Buildroot.
If Kodi really requires eventfd, we'll have to mark it incompatible with
uClibc in Buildroot. Kodi is already a big beast all by itself, so the
oversize of glibc would not be that noticeable when compared to Kodi.
Also, your use-case is a bit weird: you said you're using the fli4l
project to run Kodi on it. We failed to see the relation with Buildroot.
As such, we're marking this patch "Rejected" in Patchwork.
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2014-12-08 22:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-24 20:43 [Buildroot] [PATCH 1/1] package/uclibc: Add eventfd_read() and eventfd_write() Bernd Kuhls
2014-10-25 0:16 ` Peter Korsgaard
2014-10-25 18:22 ` Bernd Kuhls
2014-10-25 23:51 ` Peter Korsgaard
2014-10-26 14:15 ` Bernd Kuhls
2014-12-08 22:25 ` Yann E. MORIN [this message]
2014-12-14 10:36 ` Bernd Kuhls
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=20141208222547.GE4105@free.fr \
--to=yann.morin.1998@free.fr \
--cc=buildroot@busybox.net \
/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