From: Simon Horman <horms@verge.net.au>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] ARM: shmobile: henninger: rename board to Porter
Date: Thu, 29 Jan 2015 00:30:57 +0000 [thread overview]
Message-ID: <20150129003057.GB18731@verge.net.au> (raw)
In-Reply-To: <54C8E718.7060504@cogentembedded.com>
On Wed, Jan 28, 2015 at 04:41:44PM +0300, Sergei Shtylyov wrote:
> Hello.
>
> On 1/25/2015 10:30 PM, Geert Uytterhoeven wrote:
>
> >>Renesas has made some changes to the Henninger low cost board hardware and at
> >>the same time decided to rename the board to Porter.
>
> >Which changes?
>
> I don't have a list ready, sorry. One thing I know is that HDMI chip is
> different (the same as on Koelsch now); we don't support it yet...
This sounds more like a new board than an update. I don't have any strong
opinions about this at this time but perhaps it would make more sense to
handle this as two steps: adding a new board and removing an old one.
> >They're not reflected in the new DTS?
>
> Not yet.
>
> >>Signed-off-by: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
>
> >>---
> >>This patch is against 'renesas-devel-20150123-v3.19-rc5' tag of Simon Horman's
> >>'renesas.git' repo.
> >>
> >> arch/arm/boot/dts/Makefile | 2 +-
> >> .../arm/boot/dts/{r8a7791-henninger.dts => r8a7791-porter.dts} | 10 +++++-----
> >> 2 files changed, 6 insertions(+), 6 deletions(-)
> >> rename arch/arm/boot/dts/{r8a7791-henninger.dts => r8a7791-porter.dts} (96%)
>
> >You forgot to update Documentation/devicetree/bindings/arm/shmobile.txt
>
> No wonder -- I had no idea it is listed there...
>
> >Gr{oetje,eeting}s,
>
> > Geert
>
> WBR, Sergei
>
prev parent reply other threads:[~2015-01-29 0:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-23 20:37 [PATCH] ARM: shmobile: henninger: rename board to Porter Sergei Shtylyov
2015-01-25 19:30 ` Geert Uytterhoeven
2015-01-28 13:41 ` Sergei Shtylyov
2015-01-29 0:30 ` Simon Horman [this message]
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=20150129003057.GB18731@verge.net.au \
--to=horms@verge.net.au \
--cc=linux-arm-kernel@lists.infradead.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