From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: aout-core: zero thread debug registers in a.out core dump
Date: Thu, 10 Mar 2011 13:08:33 -0000 [thread overview]
Message-ID: <000801cbdf24$425fc360$c71f4a20$@deacon@arm.com> (raw)
In-Reply-To: <AANLkTin0xzSXRPbTqYkXp+2C34Qhoy321LoLERWfvCC4@mail.gmail.com>
Hi Bryan,
> Ah, yeah, I got it.
>
> I think your patch is right, no need for me to repost. Please add my SOB
>
> Signed-off-by: Bryan Wu <bryan.wu@canonical.com>
Thanks, submitted as 6798/1. Note that the patch system didn't like the
`re:' substring of ARM: aout-core: zero ... so the patch name has been
slightly mangled.
Will
prev parent reply other threads:[~2011-03-10 13:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-08 10:57 [PATCH] ARM: aout-core: zero thread debug registers in a.out core dump Will Deacon
2011-03-10 3:43 ` Bryan Wu
2011-03-10 10:15 ` Will Deacon
[not found] ` <-4405681450588494999@unknownmsgid>
2011-03-10 11:06 ` Bryan Wu
2011-03-10 13:08 ` Will Deacon [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='000801cbdf24$425fc360$c71f4a20$@deacon@arm.com' \
--to=will.deacon@arm.com \
--cc=linux-arm-kernel@lists.infradead.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 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).