From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Simon Horman <horms@verge.net.au>, David Airlie <airlied@linux.ie>
Cc: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>,
dri-devel@lists.freedesktop.org, linux-sh@vger.kernel.org,
Magnus Damm <magnus.damm@gmail.com>,
arm@kernel.org
Subject: Re: [PATCH 0/2] Fix legacy boards compilation breakage with DU
Date: Fri, 28 Nov 2014 08:17:33 +0000 [thread overview]
Message-ID: <6028379.agoUkaPz4c@avalon> (raw)
In-Reply-To: <20141128001846.GD30850@verge.net.au>
[CCing Dave]
On Friday 28 November 2014 09:18:46 Simon Horman wrote:
> [CCed Magnus, ARM SoC maintainers]
>
> On Thu, Nov 27, 2014 at 05:19:11PM +0200, Laurent Pinchart wrote:
> > Hello,
> >
> > The DU driver has lost support for platform data, resulting in a
> > compilation breakage for the legacy Marzen and Lager board files that
> > managed to keep under the radar until now.
> >
> > As the multiplatform boards should be used instead, drop support for DU in
> > the legacy Marzen and Lager boards.
> >
> > Simon, this is required to fix a compilation breakage in the drm-next
> > branch. I'm sorry for not catching it earlier :-/ How would you like this
> > to go in ? Could the patches be applied to the DRM tree ? They seem to
> > apply cleanly to both drm-next and your latest devel branch.
> >
> > Laurent Pinchart (2):
> > ARM: shmobile: lager: Remove DU platform device
> > ARM: shmobile: marzen: Remove DU platform device
> >
> > arch/arm/mach-shmobile/board-lager.c | 58 ------------------------------
> > arch/arm/mach-shmobile/board-marzen.c | 58 ------------------------------
>
> Yes, I think that should be fine as these fines are in maintenance mode and
> the only recent change I see to them is to modify the FSF address, which
> seems far away from the hunks in this patch-set.
>
> In other words, I think the chance of conflicts is small and I am fine with
> these changes going through the DRM tree if that is where the breakage
> manifests.
>
> Acked-by: Simon Horman <horms+renesas@verge.net.au>
>
> I am of course, happy to take them if the DRM maintainer(s) prefer me to.
Dave, how would you prefer to handle this ?
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2014-11-28 8:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-27 15:19 [PATCH 0/2] Fix legacy boards compilation breakage with DU Laurent Pinchart
2014-11-27 15:19 ` [PATCH 1/2] ARM: shmobile: lager: Remove DU platform device Laurent Pinchart
2014-11-27 15:19 ` [PATCH 2/2] ARM: shmobile: marzen: " Laurent Pinchart
2014-11-28 0:18 ` [PATCH 0/2] Fix legacy boards compilation breakage with DU Simon Horman
2014-11-28 8:17 ` Laurent Pinchart [this message]
2014-12-01 15:09 ` Arnd Bergmann
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=6028379.agoUkaPz4c@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=airlied@linux.ie \
--cc=arm@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=horms@verge.net.au \
--cc=laurent.pinchart+renesas@ideasonboard.com \
--cc=linux-sh@vger.kernel.org \
--cc=magnus.damm@gmail.com \
/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).