From: Rich Felker <dalias@libc.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Bartosz Golaszewski <brgl@bgdev.pl>,
Yoshinori Sato <ysato@users.sourceforge.jp>,
"Rafael J . Wysocki" <rafael@kernel.org>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
Thomas Gleixner <tglx@linutronix.de>,
Jiri Slaby <jslaby@suse.com>,
linux-sh@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-serial@vger.kernel.org,
Bartosz Golaszewski <bgolaszewski@baylibre.com>
Subject: Re: [PATCH v4 0/2] drivers: make early_platform code SuperH-specific
Date: Fri, 4 Oct 2019 09:20:25 -0400 [thread overview]
Message-ID: <20191004132025.GQ16318@brightrain.aerifal.cx> (raw)
Message-ID: <20191004132025.6vrgVsH8Y5a7UKPa4KyGL86SRq4lbTmdz1lvkeYmQwY@z> (raw)
In-Reply-To: <20191004130031.GA596158@kroah.com>
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 <bgolaszewski@baylibre.com>
> >
> > 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.
Rich
next prev parent reply other threads:[~2019-10-04 13:35 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-03 9:29 [PATCH v4 0/2] drivers: make early_platform code SuperH-specific Bartosz Golaszewski
2019-10-03 9:29 ` Bartosz Golaszewski
2019-10-03 9:29 ` [PATCH v4 1/2] drivers: move the early platform device support to arch/sh Bartosz Golaszewski
2019-10-03 9:29 ` Bartosz Golaszewski
2019-12-02 4:14 ` Guenter Roeck
2019-12-02 7:40 ` Bartosz Golaszewski
2019-12-02 13:03 ` Guenter Roeck
2019-12-02 17:18 ` Bartosz Golaszewski
2019-12-02 17:42 ` Guenter Roeck
2019-12-03 5:24 ` Guenter Roeck
2019-12-03 9:49 ` Bartosz Golaszewski
2019-12-03 10:14 ` Geert Uytterhoeven
2019-12-03 14:36 ` Guenter Roeck
2019-10-03 9:29 ` [PATCH v4 2/2] sh: add the sh_ prefix to early platform symbols Bartosz Golaszewski
2019-10-03 9:29 ` Bartosz Golaszewski
2019-10-04 13:00 ` [PATCH v4 0/2] drivers: make early_platform code SuperH-specific Greg Kroah-Hartman
2019-10-04 13:00 ` Greg Kroah-Hartman
2019-10-04 13:20 ` Rich Felker [this message]
2019-10-04 13:20 ` Rich Felker
2019-10-07 14:44 ` Greg Kroah-Hartman
2019-10-07 14:44 ` Greg Kroah-Hartman
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=20191004132025.GQ16318@brightrain.aerifal.cx \
--to=dalias@libc.org \
--cc=bgolaszewski@baylibre.com \
--cc=brgl@bgdev.pl \
--cc=daniel.lezcano@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=tglx@linutronix.de \
--cc=ysato@users.sourceforge.jp \
/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).