From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.3 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS,USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 1EB23C4360C for ; Fri, 4 Oct 2019 13:00:36 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id E0C0121D81 for ; Fri, 4 Oct 2019 13:00:35 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1570194036; bh=5Q/iWTgymOppj9DeDqpQWfy6Ic9FHuGC0vgACNbYbd0=; h=Date:From:To:Cc:Subject:References:In-Reply-To:List-ID:From; b=Chr1p8yPR3DJ8INMCiR4t6C8PKZwwcS7xfzdl5AAFkfWnp461qeaYc8b24RwK8hK8 mzzhhbTMJ1upMBbSEmaDjrGi8BB/H4c5lBDkrmiUVX9rT+t91oo2t3UfhozvVWhFYf PywXao3ke05m7SHpjeBtpSQeHqJ/9JKL+hwZd1AQ= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2388020AbfJDNAf (ORCPT ); Fri, 4 Oct 2019 09:00:35 -0400 Received: from mail.kernel.org ([198.145.29.99]:36284 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2387593AbfJDNAe (ORCPT ); Fri, 4 Oct 2019 09:00:34 -0400 Received: from localhost (83-86-89-107.cable.dynamic.v4.ziggo.nl [83.86.89.107]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id D7B73207FF; Fri, 4 Oct 2019 13:00:32 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1570194033; bh=5Q/iWTgymOppj9DeDqpQWfy6Ic9FHuGC0vgACNbYbd0=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=jeWNxAVjM4M9jRnwjBw1GFUCfukHqXGsDW5rJu7N0l04+zMSDtyZVPUWlR7BmlWPW Pf8rFwhCg6vy/1UMQMas0rybf6WEZzSjEubo9xj49BqcCMo8veo/EBye4ja8KOnHZd iPIwswtomqveq0U9KIpbFVNiWnUPXYYEX4JVu/C8= Date: Fri, 4 Oct 2019 15:00:31 +0200 From: Greg Kroah-Hartman To: Bartosz Golaszewski Cc: Yoshinori Sato , Rich Felker , "Rafael J . Wysocki" , Daniel Lezcano , Thomas Gleixner , Jiri Slaby , linux-sh@vger.kernel.org, linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org, Bartosz Golaszewski Subject: Re: [PATCH v4 0/2] drivers: make early_platform code SuperH-specific Message-ID: <20191004130031.GA596158@kroah.com> References: <20191003092913.10731-1-brgl@bgdev.pl> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20191003092913.10731-1-brgl@bgdev.pl> User-Agent: Mutt/1.12.2 (2019-09-21) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Oct 03, 2019 at 11:29:11AM +0200, Bartosz Golaszewski wrote: > From: Bartosz Golaszewski > > Some time ago I started a discussion about the need for a proper early device > probing mechanism[1]. One that would be based on real platform drivers and > support both platform data and device tree. > > While we're far from reaching any consensus on the implementation, Arnd > suggested that I start off by moving the SuperH-specific early platform > drivers implementation to arch/sh[2]. > > This series is the first attempt at making way for a new, less hacky > implementation. > > The first patch moves all the early_platform code to arch/sh. > > The second patch prefixes all early_platform symbols with 'sh_'. > > [1] https://lkml.org/lkml/2018/4/26/657 > [2] https://lkml.org/lkml/2018/4/27/239 > > v1 -> v2: > - certain drivers are compiled for arm/mach-shmobile too - we need to > add ifdefs for CONFIG_SUPERH around early_platform calls > > v2 -> v3: > - added a stub for is_early_platform_device() which always returns false > on non-SuperH architectures > > v3 -> v4: > - rebased on top of v5.4-rc1 > - removed patches that are already upstream from the series > > Bartosz Golaszewski (2): > drivers: move the early platform device support to arch/sh > sh: add the sh_ prefix to early platform symbols I like this, any objection from anyone if I take this in my driver-core tree for 5.5-rc1? thanks, greg k-h