From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH 0/5] R-Car Gen2 removal and cleanups
Date: Thu, 04 Dec 2014 07:32:49 +0000 [thread overview]
Message-ID: <1471311.k3jFKy5IOE@avalon> (raw)
In-Reply-To: <1417538146-23350-1-git-send-email-laurent.pinchart+renesas@ideasonboard.com>
Hi Simon,
On Thursday 04 December 2014 15:47:31 Simon Horman wrote:
> On Tue, Dec 02, 2014 at 11:44:29PM +0200, Laurent Pinchart wrote:
> > On Tuesday 02 December 2014 22:06:49 Geert Uytterhoeven wrote:
> >> On Tue, Dec 2, 2014 at 5:35 PM, Laurent Pinchart wrote:
> >>> This patch series remove the Lager legacy and reference board files
> >>> from the kernel. It builds upon two patches previously posted by
> >>> Magnus and updated to removal left-overs.
> >>>
> >>> The rationale for the change, beside keeping the ARM SoC maintainers
> >>> happy, is that the Lager board is now correctly supported using DT
> >>> boot and generic code only, so there's no reason to keep board files
> >>> along.
> >>
> >> Acked-by: Geert Uytterhoeven <geert+renesas@glider.be>
> >>
> >>> The second reason to repost the patches is to include a pet peeve of
> >>> mine that I've been carrying in my local branches for too long. The
> >>> last two patches update the Lager and Koelsch DT files to finally
> >>> rename the two serial ports to ttySC0 and ttySC1.
> >>
> >> I'm not opposed to this change.
>
> IIRC, this has been a contentious issue in the past.
> I will confer with Magnus to make sure we are all happy with this change.
If I recall correctly the major issue back then was synchronization of serial
port names between legacy and DT boot. Now that Lager and Koelsch legacy have
been removed, there should at least be no synchronization issue anymore. I'll
wait for feedback from Magnus of course.
> >>> The patches are targeted at v3.20, as they depend on the "ARM:
> >>> shmobile:
> >>> lager: Remove DU platform device" patch scheduled for merge in
> >>> v3.19-rc1 through the DRM tree.
> >>
> >> Given the issues with armadillo-legacy (and perhaps some other -legacy
> >> platform(s)?) in -next (https://lkml.org/lkml/2014/12/2/339), we may
> >> have to accelerate kicking out -legacy...
> >
> > We've known for a long time that -legacy is doomed. Now it's a question of
> > priorities :-)
>
> Zero argument there.
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2014-12-04 7:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-02 16:35 [PATCH 0/5] R-Car Gen2 removal and cleanups Laurent Pinchart
2014-12-02 21:06 ` Geert Uytterhoeven
2014-12-02 21:44 ` Laurent Pinchart
2014-12-04 6:47 ` Simon Horman
2014-12-04 7:32 ` Laurent Pinchart [this message]
2014-12-04 7:40 ` Magnus Damm
2014-12-04 7:44 ` Simon Horman
2014-12-04 7:45 ` Simon Horman
2014-12-04 9:05 ` Geert Uytterhoeven
2014-12-04 9:12 ` Laurent Pinchart
2014-12-04 12:18 ` Simon Horman
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=1471311.k3jFKy5IOE@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=linux-sh@vger.kernel.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).