From: Tom Rini <trini@kernel•crashing.org>
To: Sylvain Munaut <tnt@246tNt•com>
Cc: LKML <linux-kernel@vger•kernel.org>,
Embedded PPC Linux list <linuxppc-embedded@ozlabs•org>
Subject: Re: [PATCH 1/2] MPC52xx updates : sparse clean-ups
Date: Fri, 11 Mar 2005 14:00:52 -0700 [thread overview]
Message-ID: <20050311210052.GC3098@smtp.west.cox.net> (raw)
In-Reply-To: <423203EC.1070003@246tNt.com>
On Fri, Mar 11, 2005 at 09:47:40PM +0100, Sylvain Munaut wrote:
[snip]
> static struct hw_interrupt_type mpc52xx_ic = {
> - "MPC52xx",
[snip]
> + .typename = "MPC52xx",
Shouldn't that be " MPC52xx ", or is that another field I'm thinking
of?
--
Tom Rini
http://gate.crashing.org/~trini/
prev parent reply other threads:[~2005-03-11 21:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-11 20:05 [PATCH 1/2] MPC52xx updates : sparse clean-ups Sylvain Munaut
2005-03-11 20:08 ` [PATCH 2/2] MPC52xx updates : PCI Support Sylvain Munaut
2005-03-11 20:48 ` Dale Farnsworth
2005-03-11 21:06 ` Sylvain Munaut
2005-03-11 20:12 ` [PATCH 1/2] MPC52xx updates : sparse clean-ups Kumar Gala
2005-03-11 20:47 ` Sylvain Munaut
2005-03-11 21:00 ` Tom Rini [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=20050311210052.GC3098@smtp.west.cox.net \
--to=trini@kernel$(echo .)crashing.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linuxppc-embedded@ozlabs$(echo .)org \
--cc=tnt@246tNt$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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