[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20090504135327.13cd42af.akpm@linux-foundation.org>
Date: Mon, 4 May 2009 13:53:27 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Anton Vorontsov <avorontsov@...mvista.com>
Cc: galak@...nel.crashing.org, dbrownell@...rs.sourceforge.net,
linuxppc-dev@...abs.org, spi-devel-general@...ts.sourceforge.net,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 9/9] spi_mpc8xxx: s/83xx/8xxx/g
On Fri, 1 May 2009 03:48:33 +0400
Anton Vorontsov <avorontsov@...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 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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists