From: "Alex Bennée" <alex.bennee@linaro.org>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Riku Voipio <riku.voipio@linaro.org>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH 3/4] linux-user: set minimum kernel version to2.6.322
Date: Tue, 04 Mar 2014 16:31:22 +0000 [thread overview]
Message-ID: <87mwh6c4ds.fsf@linaro.org> (raw)
In-Reply-To: <CAFEAcA9O-Ue-xxiHOB3_6Yau2trGNi7T2hVhpV9pMNg176YMSA@mail.gmail.com>
Peter Maydell <peter.maydell@linaro.org> writes:
> On 4 March 2014 11:32, Alex Bennée <alex.bennee@linaro.org> wrote:
>>
>> riku.voipio@linaro.org writes:
>>
>>> From: Riku Voipio <riku.voipio@linaro.org>
>>>
>>> Popular glibc based distributions[1] require minimum
>>> 2.6.32 as kernel version. For some targets 2.6.18
>>> would be enough, but dropping so low would mean some
>>> suboptimal system calls could get used.
<snip>
>>It would be nice to
>> have an upstream fix for the hacks the distros are adding.
>
> I think that's what this patchset is supposed to be :-)
>
>> I believe they are patching UNAME to 3.7.0 for aarch64.
>
> Only to the extent that they're still carrying bogus patches
> borrowed from the SuSE tree rather than using the better
> way of setting per-arch minumum reported uname that we
> applied upstream.
<snip>
Only I didn't see linux-user/aarch64 in the diffstat, or did I miss
another patch?
--
Alex Bennée
next prev parent reply other threads:[~2014-03-04 16:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-04 3:22 [Qemu-devel] [PATCH 3/4] linux-user: set minimum kernel version to 2.6.32 riku.voipio
2014-03-04 11:32 ` [Qemu-devel] [PATCH 3/4] linux-user: set minimum kernel version to2.6.322 Alex Bennée
2014-03-04 11:41 ` Peter Maydell
2014-03-04 16:31 ` Alex Bennée [this message]
2014-03-04 16:41 ` Peter Maydell
2014-03-04 17:38 ` Alex Bennée
2014-03-07 2:19 ` Riku Voipio
2014-03-07 8:45 ` Peter Maydell
2014-03-10 12:00 ` Riku Voipio
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=87mwh6c4ds.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=riku.voipio@linaro.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.