On Wed, Jul 23, 2014 at 10:49:01AM -0700, Olof Johansson wrote: > On Wed, Jul 23, 2014 at 10:41 AM, Greg Kroah-Hartman > <gregkh@xxxxxxxxxxxxxxxxxxx> wrote: > > On Wed, Jul 23, 2014 at 06:07:18PM +0100, Pawel Moll wrote: > >> A number of board files in arch/arm and arch/unicore32 > >> explicitly reference platform_bus device as a parent > >> for new platform devices. > >> > >> This is unnecessary, as platform device API guarantees > >> that devices with NULL parent are going to by adopted > >> by the mentioned "root" device. > >> > >> This patch removes or replaces with NULL such references. > >> > >> Signed-off-by: Pawel Moll <pawel.moll@xxxxxxx> > >> --- > >> arch/arm/mach-bcm/board_bcm21664.c | 3 +-- > >> arch/arm/mach-bcm/board_bcm281xx.c | 3 +-- > >> arch/arm/mach-clps711x/board-edb7211.c | 6 +++--- > >> arch/arm/mach-clps711x/board-p720t.c | 6 +++--- > >> arch/arm/mach-imx/mach-mx27ads.c | 2 +- > >> arch/arm/mach-shmobile/board-ape6evm.c | 14 +++++++------- > >> arch/arm/mach-shmobile/board-bockw.c | 19 ++++++++---------- > >> arch/arm/mach-shmobile/board-genmai.c | 5 ++--- > >> arch/arm/mach-shmobile/board-koelsch.c | 26 ++++++++++++------------- > >> arch/arm/mach-shmobile/board-lager.c | 34 ++++++++++++++------------------- > >> arch/arm/mach-shmobile/board-marzen.c | 1 - > >> arch/arm/mach-shmobile/setup-r7s72100.c | 2 +- > >> arch/arm/mach-shmobile/setup-r8a73a4.c | 8 ++++---- > >> arch/arm/mach-shmobile/setup-r8a7778.c | 13 ++++++------- > >> arch/arm/mach-shmobile/setup-r8a7779.c | 6 +++--- > >> arch/arm/mach-shmobile/setup-r8a7790.c | 10 +++++----- > >> arch/arm/mach-shmobile/setup-r8a7791.c | 8 ++++---- > >> arch/unicore32/kernel/puv3-core.c | 2 +- > >> arch/unicore32/kernel/puv3-nb0916.c | 6 +++--- > >> 19 files changed, 79 insertions(+), 95 deletions(-) > > > > Looks good, if there are no objections, I'll take this through my > > driver-core tree, so that your follow-on patches that change things will > > still apply. > > Acked-by: Olof Johansson <olof@xxxxxxxxx> > > Just in case we end up having dependent patches and/or lots of > conflicts, can you stick these on a short topic branch that we can > also pull in? Hm, I don't normally do "short topic branches", so I've just stuck it into my driver-core-next branch of my driver-core.git tree on kernel.org. I doubt the "make platform_bus static" or "make it a platform device" will happen soon, given my questions on the other patch in this series. thanks, greg k-h -- To unsubscribe from this list: send the line "unsubscribe linux-tegra" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
