From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] xinetd: Patch configure script to fix rlim_t test
Date: Sun, 21 Sep 2014 20:10:30 +0200 [thread overview]
Message-ID: <20140921201030.0ea3b3de@free-electrons.com> (raw)
In-Reply-To: <1410882141-16213-1-git-send-email-maarten@treewalker.org>
Dear Maarten ter Huurne,
On Tue, 16 Sep 2014 17:42:21 +0200, Maarten ter Huurne wrote:
> Fixes build with musl libc.
>
> Signed-off-by: Maarten ter Huurne <maarten@treewalker.org>
> ---
> package/xinetd/xinetd-005-configure-rlim_t.patch | 18 ++++++++++++++++++
> 1 file changed, 18 insertions(+)
> create mode 100644 package/xinetd/xinetd-005-configure-rlim_t.patch
I've renamed the patch to use the 004 sequence number, which wasn't
used.
Applied, thanks a lot! Please don't forget to submit upstream if it's
not already done.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2014-09-21 18:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-16 15:42 [Buildroot] [PATCH] xinetd: Patch configure script to fix rlim_t test Maarten ter Huurne
2014-09-21 18:10 ` Thomas Petazzoni [this message]
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=20140921201030.0ea3b3de@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--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