From: Shaun Jackman <sjackman@gmail.com>
To: gdb-patches@sources.redhat.com
Subject: Re: sim/arm RedBoot meminfo syscall [PATCH]
Date: Thu, 02 Feb 2006 13:49:00 -0000 [thread overview]
Message-ID: <7f45d9390602020549n61b8ea42n247eefb77d058fc8@mail.gmail.com> (raw)
In-Reply-To: <20060202014949.GB19694@nevyn.them.org>
On 2/1/06, Daniel Jacobowitz <drow@false.org> wrote:
> Sorry, I forgot that you didn't have write access. I've checked it in.
> Small comment, since there's a changelog in sim/arm/, you don't need
> sim/arm/ on front of the log entry.
Thanks, Daniel.
> If you'd like to have write access for the future, fill out the form on
> sourceware.org (search for "handy dandy little form") and list me as
> your approval.
OK. Will do. I have a patch sitting around for some simple Linux
syscall support for sim/arm/armos.c. Perhaps I'll use that for my
first check in, after approval of course.
Cheers,
Shaun
prev parent reply other threads:[~2006-02-02 13:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-17 22:46 Shaun Jackman
2006-01-23 2:01 ` Daniel Jacobowitz
2006-01-23 15:57 ` Richard Earnshaw
2006-01-23 16:03 ` Daniel Jacobowitz
2006-01-24 23:19 ` Shaun Jackman
2006-02-02 1:49 ` Daniel Jacobowitz
2006-02-02 13:49 ` Shaun Jackman [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=7f45d9390602020549n61b8ea42n247eefb77d058fc8@mail.gmail.com \
--to=sjackman@gmail.com \
--cc=gdb-patches@sources.redhat.com \
/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