linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: olof@lixom.net (Olof Johansson)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 1/2] platform: Remove most references to platform_bus device
Date: Wed, 23 Jul 2014 10:49:01 -0700	[thread overview]
Message-ID: <CAOesGMiGzfwLZvkxzzQQ0k4M7i2VukrCHGXCrFhZ6A3mkjVbiw@mail.gmail.com> (raw)
In-Reply-To: <20140723174137.GC16664@kroah.com>

On Wed, Jul 23, 2014 at 10:41 AM, Greg Kroah-Hartman
<gregkh@linuxfoundation.org> 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@arm.com>
>> ---
>>  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@lixom.net>

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?

Thanks,

-Olof

  reply	other threads:[~2014-07-23 17:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-23 17:07 [PATCH v4 1/2] platform: Remove most references to platform_bus device Pawel Moll
2014-07-23 17:07 ` [PATCH v4 2/2] platform: Make platform_bus device a platform device Pawel Moll
2014-07-23 17:40   ` Greg Kroah-Hartman
2014-07-23 18:53   ` Olof Johansson
2014-07-23 17:41 ` [PATCH v4 1/2] platform: Remove most references to platform_bus device Greg Kroah-Hartman
2014-07-23 17:49   ` Olof Johansson [this message]
2014-07-24  2:14     ` Greg Kroah-Hartman
2014-07-24  2:48       ` Olof Johansson

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=CAOesGMiGzfwLZvkxzzQQ0k4M7i2VukrCHGXCrFhZ6A3mkjVbiw@mail.gmail.com \
    --to=olof@lixom.net \
    --cc=linux-arm-kernel@lists.infradead.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).