From: Meador Inge <meadori@codesourcery.com>
To: Riku Voipio <riku.voipio@iki.fi>
Cc: qemu-devel@nongnu.org, "Andreas Färber" <afaerber@suse.de>
Subject: Re: [Qemu-devel] [PATCH v1 1/1] syscall: #ifdef newer RLIMIT_* codes
Date: Tue, 27 Mar 2012 15:20:09 -0500 [thread overview]
Message-ID: <4F7220F9.10305@codesourcery.com> (raw)
In-Reply-To: <20120327171554.GA16571@afflict.kos.to>
On 03/27/2012 12:15 PM, Riku Voipio wrote:
> Hi,
>
> Do we really need this? 2.6.12 came out in 2005, even oldest supported
> RHEL (5) is minimum 2.6.18 these days.
The development environment I am working with uses a RHEL 3 compatible sysroot
(RHEL 3 is currently marked with "extended life cycle support"). So, I
definitely need it :-) (and yes I know that this sysroot is ancient). I don't
know if others are using such old development sysroots. The changes are
minimal and while it would be great to have this applied upstream I do
understand if you want to NACK.
--
Meador Inge
CodeSourcery / Mentor Embedded
http://www.mentor.com/embedded-software
prev parent reply other threads:[~2012-03-27 20:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-20 18:26 [Qemu-devel] [PATCH v1 1/1] syscall: #ifdef newer RLIMIT_* codes Meador Inge
2012-02-20 19:38 ` Andreas Färber
2012-03-27 15:08 ` Meador Inge
2012-03-27 17:15 ` Riku Voipio
2012-03-27 20:20 ` Meador Inge [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=4F7220F9.10305@codesourcery.com \
--to=meadori@codesourcery.com \
--cc=afaerber@suse.de \
--cc=qemu-devel@nongnu.org \
--cc=riku.voipio@iki.fi \
/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).