qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: <cedric.vincent@st.com>
To: "riku.voipio@iki.fi" <riku.voipio@iki.fi>
Cc: Laurent ALFONSI <Laurent.ALFONSI@st.com>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH 09/18] linux-user: Define AT_RANDOM to support target stack protection mechanism.
Date: Tue, 21 Jun 2011 09:05:19 +0200	[thread overview]
Message-ID: <20110621070518.GA25342@gnx2503> (raw)
In-Reply-To: <fad3dcb536b4cc41aa93225f8ecc899d9d320fa6.1308583801.git.riku.voipio@iki.fi>

On Mon, Jun 20, 2011 at 06:20:14PM +0200, riku.voipio@iki.fi wrote:
> 
> 8<----8<----8<----8<----8<----8<----8<----8<----8<----8<----8<----8<----

Looks like this mail was not extracted with "--scissors", the text
above this line is not part of the commit message.

Regards,
Cédric.

  reply	other threads:[~2011-06-21  7:08 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-20 16:20 [Qemu-devel] [PATCH 00/18] pending linux-user patches riku.voipio
2011-06-20 16:20 ` [Qemu-devel] [PATCH 01/18] Don't translate pointer when in restore_sigcontext riku.voipio
2011-06-20 16:20 ` [Qemu-devel] [PATCH 02/18] linux-user: Fix the load of ELF files that have no "useful" symbol riku.voipio
2011-06-21  7:07   ` cedric.vincent
2011-06-20 16:20 ` [Qemu-devel] [PATCH 03/18] linux-user: Handle images where lowest vaddr is not page aligned riku.voipio
2011-06-20 16:20 ` [Qemu-devel] [PATCH 04/18] linux-user: Don't use MAP_FIXED in do_brk() riku.voipio
2011-06-20 16:20 ` [Qemu-devel] [PATCH 05/18] arm-semi.c: Use correct check for failure of do_brk() riku.voipio
2011-06-20 16:20 ` [Qemu-devel] [PATCH 06/18] m68k-semi.c: " riku.voipio
2011-06-20 16:20 ` [Qemu-devel] [PATCH 07/18] linux-user: Fix the computation of the requested heap size riku.voipio
2011-06-21  7:11   ` cedric.vincent
2011-06-21 17:50     ` Riku Voipio
2011-06-20 16:20 ` [Qemu-devel] [PATCH 08/18] linux-user: add pselect6 syscall support riku.voipio
2011-06-20 16:20 ` [Qemu-devel] [PATCH 09/18] linux-user: Define AT_RANDOM to support target stack protection mechanism riku.voipio
2011-06-21  7:05   ` cedric.vincent [this message]
2011-06-20 16:20 ` [Qemu-devel] [PATCH 10/18] linuxload: id_change was a write only variable riku.voipio
2011-06-20 16:20 ` [Qemu-devel] [PATCH 11/18] syscall: really return ret code riku.voipio
2011-06-20 16:20 ` [Qemu-devel] [PATCH 12/18] linux-user: syscall should use sanitized arg1 riku.voipio
2011-06-20 16:20 ` [Qemu-devel] [PATCH 13/18] flatload: end_code was only used in a debug message riku.voipio
2011-06-20 16:20 ` [Qemu-devel] [PATCH 14/18] flatload: memp was a write-only variable riku.voipio
2011-06-20 16:20 ` [Qemu-devel] [PATCH 15/18] linux-user: Bump do_syscall() up to 8 syscall arguments riku.voipio
2011-06-20 16:20 ` [Qemu-devel] [PATCH 16/18] linux-user/signal.c: Remove only-ever-set variable fpu_save_addr riku.voipio
2011-06-20 16:20 ` [Qemu-devel] [PATCH 17/18] linux-user/signal.c: Remove unused fenab riku.voipio
2011-06-20 16:20 ` [Qemu-devel] [PATCH 18/18] linux-user: Fix sync_file_range on 32bit mips 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=20110621070518.GA25342@gnx2503 \
    --to=cedric.vincent@st.com \
    --cc=Laurent.ALFONSI@st.com \
    --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).