From: Kumar Gala <galak@kernel.crashing.org>
To: Dave Kleikamp <shaggy@linux.vnet.ibm.com>
Cc: linuxppc-dev list <Linuxppc-dev@ozlabs.org>
Subject: Re: [PATCH] powerpc/booke: Fix a couple typos in the advanced ptrace code
Date: Thu, 4 Mar 2010 10:52:24 -0600 [thread overview]
Message-ID: <F7E89511-3938-47DC-A6EF-74F8A4B81471@kernel.crashing.org> (raw)
In-Reply-To: <1266954197.11207.20.camel@norville.austin.ibm.com>
On Feb 23, 2010, at 1:43 PM, Dave Kleikamp wrote:
> powerpc/booke: Fix a couple typos in the advanced ptrace code
>
> Found and fixed a couple typos in the advanced ptrace patches.
> (These patches are currently in benh's next tree.)
>
> Signed-off-by: Dave Kleikamp <shaggy@linux.vnet.ibm.com>
> Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>
> Cc: linuxppc-dev list <Linuxppc-dev@ozlabs.org>
>
> ---
Acked-by: Kumar Gala <galak@kernel.crashing.org>
- k
prev parent reply other threads:[~2010-03-04 16:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-08 21:50 [PATCH 00/04] powerpc/booke: Expose advanced debug registers through extended ptrace interface Dave Kleikamp
2010-02-08 21:50 ` [PATCH 01/04] powerpc/booke: Introduce new CONFIG options for advanced debug registers Dave Kleikamp
2010-02-11 3:55 ` David Gibson
2010-02-08 21:51 ` [PATCH 02/04] powerpc: Extended ptrace interface Dave Kleikamp
2010-02-08 21:51 ` [PATCH 04/04] powerpc/booke: Add support for advanced debug registers Dave Kleikamp
2010-02-08 21:53 ` [PATCH 03/04] powerpc/booke: Add definitions " Dave Kleikamp
2010-02-23 19:43 ` [PATCH] powerpc/booke: Fix a couple typos in the advanced ptrace code Dave Kleikamp
2010-03-01 14:57 ` [PATCH] powerpc/booke: Fix breakpoint/watchpoint one-shot behavior Dave Kleikamp
2010-03-04 16:52 ` Kumar Gala [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=F7E89511-3938-47DC-A6EF-74F8A4B81471@kernel.crashing.org \
--to=galak@kernel.crashing.org \
--cc=Linuxppc-dev@ozlabs.org \
--cc=shaggy@linux.vnet.ibm.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