From: Gary Thomas <gary@mlbassoc.com>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org,
David Brownell <dbrownell@users.sourceforge.net>
Subject: Re: [PATCH 1/3] spi_mpc83xx: Handles other Freescale processors
Date: Mon, 06 Apr 2009 08:33:43 -0600 [thread overview]
Message-ID: <49DA12C7.9000900@mlbassoc.com> (raw)
In-Reply-To: <6758B03E-2525-4754-83FA-643CED277CC6@kernel.crashing.org>
Kumar Gala wrote:
>
> On Apr 4, 2009, at 2:28 PM, Anton Vorontsov wrote:
>
>> With this patch we'll able to select spi_mpc83xx driver on the MPC86xx
>> platforms. Let the driver depend on FSL_SOC, so we don't have to worry
>> about Kconfig anymore.
>>
>> Also remove the "experimental" dependency, the driver has been tested
>> to work on a various hardware, and surely not experimental anymore.
>>
>> Signed-off-by: Anton Vorontsov <avorontsov@ru.mvista.com>
>> ---
>> drivers/spi/Kconfig | 14 ++++++--------
>> 1 files changed, 6 insertions(+), 8 deletions(-)
>
> this looks fine, but why don't we go ahead and rename things as well?
> SPI_MPC83xx -> SPI_MPC8xxx, spi_mpc83xx.c -> spi_mpc8xxx.c
mpc8xxx implies mpc82xx (e.g. mpc8272) which is not the same controller
as on the mpc83xx
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next prev parent reply other threads:[~2009-04-06 14:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-04 19:28 [PATCH 1/3] spi_mpc83xx: Handles other Freescale processors Anton Vorontsov
2009-04-06 14:13 ` Kumar Gala
2009-04-06 14:33 ` Gary Thomas [this message]
2009-04-06 14:36 ` 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=49DA12C7.9000900@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=akpm@linux-foundation.org \
--cc=dbrownell@users.sourceforge.net \
--cc=galak@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--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).