From mboxrd@z Thu Jan 1 00:00:00 1970 From: Greg Kroah-Hartman Date: Mon, 07 Oct 2019 14:44:21 +0000 Subject: Re: [PATCH v4 0/2] drivers: make early_platform code SuperH-specific Message-Id: <20191007144421.GA966763@kroah.com> List-Id: References: <20191003092913.10731-1-brgl@bgdev.pl> <20191004130031.GA596158@kroah.com> <20191004132025.GQ16318@brightrain.aerifal.cx> In-Reply-To: <20191004132025.GQ16318@brightrain.aerifal.cx> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Rich Felker Cc: Bartosz Golaszewski , Yoshinori Sato , "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 On Fri, Oct 04, 2019 at 09:20:25AM -0400, Rich Felker wrote: > On Fri, Oct 04, 2019 at 03:00:31PM +0200, Greg Kroah-Hartman wrote: > > 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? > > I don't think I have any objection. It will probably make gratuitous > merge conflicts with Sato-san's old device tree sh4 work when we get > back to finishing that, but that's not really a big deal. Ok, I've queued it up in my tree now, thanks, greg k-h 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 3247DC47404 for ; Mon, 7 Oct 2019 14:44:26 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 0958721655 for ; Mon, 7 Oct 2019 14:44:26 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1570459466; bh=VtWId5vYYsclunErfb5u6anv5q7krptmTQWAa+3fm0o=; h=Date:From:To:Cc:Subject:References:In-Reply-To:List-ID:From; b=jl4mxpCRNtH/RRgtW5aJ+aFIj4O2J01kfg+CYBK15fllN2PBPzd+JGGFJcm/e1oTF yV21xeemgXsX+vekLz2xHcgphtSyIiJREbe+FVahwthqlqizCWmPr2CbyOrt6uURUM 1K3DBZa0GRJi2cCayurjeIt499V0RmtkbmrKfAMw= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728031AbfJGOoZ (ORCPT ); Mon, 7 Oct 2019 10:44:25 -0400 Received: from mail.kernel.org ([198.145.29.99]:55248 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727490AbfJGOoY (ORCPT ); Mon, 7 Oct 2019 10:44:24 -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 BAD9D21721; Mon, 7 Oct 2019 14:44:23 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1570459464; bh=VtWId5vYYsclunErfb5u6anv5q7krptmTQWAa+3fm0o=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=y/zA5wDpgBSS11fa0DPaotgCqyxAoUoP9sjoIkwDWeErZuOUvC9zQ1cht0PlgJCz7 oDOWEFjt3bzZFMMkF97mKTsU/ISIiQrBAPj2O+qpMWGY2JRAVAA9w6qLmhdCbLR5Qq c2q9JMvQKLIEaZvl2XAwY0aDEx/POtvwuHZgOkxc= Date: Mon, 7 Oct 2019 16:44:21 +0200 From: Greg Kroah-Hartman To: Rich Felker Cc: Bartosz Golaszewski , Yoshinori Sato , "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: <20191007144421.GA966763@kroah.com> References: <20191003092913.10731-1-brgl@bgdev.pl> <20191004130031.GA596158@kroah.com> <20191004132025.GQ16318@brightrain.aerifal.cx> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20191004132025.GQ16318@brightrain.aerifal.cx> 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 Fri, Oct 04, 2019 at 09:20:25AM -0400, Rich Felker wrote: > On Fri, Oct 04, 2019 at 03:00:31PM +0200, Greg Kroah-Hartman wrote: > > 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? > > I don't think I have any objection. It will probably make gratuitous > merge conflicts with Sato-san's old device tree sh4 work when we get > back to finishing that, but that's not really a big deal. Ok, I've queued it up in my tree now, thanks, greg k-h