From: Kumar Gala <galak@kernel.crashing.org>
To: Felix Radensky <felix@embedded-sol.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] powerpc/85xx: Added 36-bit physical device tree for mpc8572ds board
Date: Tue, 11 Aug 2009 08:33:53 -0500 [thread overview]
Message-ID: <FFAF330C-4FAF-46EA-A7E3-8D66A18880DA@kernel.crashing.org> (raw)
In-Reply-To: <4A811B4F.905@embedded-sol.com>
On Aug 11, 2009, at 2:18 AM, Felix Radensky wrote:
> Hi, Kumar
>
> Patch subject does not match the contents. The patch is about
> mpc8536ds.
>
> Felix.
Oops, copy/paste error on my part. The subject is the one that is
wrong.
- k
next prev parent reply other threads:[~2009-08-11 13:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-07 2:08 [PATCH] powerpc/85xx: Added 36-bit physical device tree for mpc8572ds board Kumar Gala
2009-08-11 7:18 ` Felix Radensky
2009-08-11 13:33 ` Kumar Gala [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-02-10 4:05 [PATCH] powerpc/85xx: Fixed PCI IO region sizes in mpc8572ds*.dts Kumar Gala
2009-02-10 4:05 ` [PATCH] powerpc/85xx: Added 36-bit physical device tree for mpc8572ds board Kumar Gala
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=FFAF330C-4FAF-46EA-A7E3-8D66A18880DA@kernel.crashing.org \
--to=galak@kernel.crashing.org \
--cc=felix@embedded-sol.com \
--cc=linuxppc-dev@ozlabs.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).