lkml.org 
[lkml]   [2009]   [May]   [4]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH 9/9] spi_mpc8xxx: s/83xx/8xxx/g
On Mon, May 04, 2009 at 01:53:27PM -0700, Andrew Morton wrote:
> On Fri, 1 May 2009 03:48:33 +0400
> Anton Vorontsov <avorontsov@ru.mvista.com> wrote:
>
> > Since we renamed the file, we might want to rename the file
> > internals too.
> >
> > Though we don't bother with changing platform driver name and
> > platform module alias. The stuff is legacy and hopefully we'll
> > remove it soon.
> >
>
> but but but
>
> >
> > -static struct of_platform_driver of_mpc83xx_spi_driver = {
> > - .name = "mpc83xx_spi",
> > - .match_table = of_mpc83xx_spi_match,
> > - .probe = of_mpc83xx_spi_probe,
> > - .remove = __devexit_p(of_mpc83xx_spi_remove),
> > +static struct of_platform_driver of_mpc8xxx_spi_driver = {
> > + .name = "mpc8xxx_spi",
> > + .match_table = of_mpc8xxx_spi_match,
> > + .probe = of_mpc8xxx_spi_probe,
> > + .remove = __devexit_p(of_mpc8xxx_spi_remove),
> > };
>
> It _did_ change the platform driver name, didn't it?

This is an OF platform driver, here it is safe to change
the name. But I didn't change the pure platform driver,
here:

| -static struct platform_driver mpc83xx_spi_driver = {
| - .probe = plat_mpc83xx_spi_probe,
| - .remove = __exit_p(plat_mpc83xx_spi_remove),
| +static struct platform_driver mpc8xxx_spi_driver = {
| + .probe = plat_mpc8xxx_spi_probe,
| + .remove = __exit_p(plat_mpc8xxx_spi_remove),
| .driver = {
| .name = "mpc83xx_spi",

------------------^

> This patch series had quite a lot of conflicts with the already-pending
>
> spi-move-common-spi_setup-functionality-into-core.patch
> spi-move-more-spi_setup-functionality-into-core.patch
>
> which I beleive I successfully fixed up.

Thanks a lot, I'll test it soon.

--
Anton Vorontsov
email: cbouatmailru@gmail.com
irc://irc.freenode.net/bd2


\
 
 \ /
  Last update: 2009-05-05 01:39    [W:0.331 / U:0.124 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site