SUPERH platform development
 help / color / mirror / Atom feed
From: Simon Horman <horms@verge.net.au>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH 03/03] ARM: shmobile: mackerel: Remove legacy board support
Date: Wed, 29 Oct 2014 23:53:35 +0000	[thread overview]
Message-ID: <20141029235335.GB4599@verge.net.au> (raw)
In-Reply-To: <20141029074717.405.8623.sendpatchset@w520>

On Wed, Oct 29, 2014 at 10:24:38AM +0100, Geert Uytterhoeven wrote:
> Hi Magnus,
> 
> On Wed, Oct 29, 2014 at 10:13 AM, Magnus Damm <magnus.damm@gmail.com> wrote:
> > I do think
> > we can ditch the bindings since we phase out the board support, but
> > perhaps that's wrong. =)
> 
> The DTS only contains the memory node, which we can easily resurrect,
> if needed.
> 
> > Do you think it is good timing to get rid of Mackerel now, or do you
> > prefer to wait?
> 
> I think the Mackerel-specific code can go.
> 
> The sh7372 SoC code is still there. That contains some still interesting parts
> (cpuidle and wake-up source code). If they can stay for a little
> while, I'm happy.

From my point of view I don't see a lot of value in keeping unused SoC code
lying around. For one thing it will be hard to avoid bitrot if we can't
even boot the code. So I'd prefer to remove sh7372 SoC code and Mackerel board
code in one hit. But I am prepared to be convinced otherwise.

      parent reply	other threads:[~2014-10-29 23:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-29  7:47 [PATCH 03/03] ARM: shmobile: mackerel: Remove legacy board support Magnus Damm
2014-10-29  8:59 ` Geert Uytterhoeven
2014-10-29  9:13 ` Magnus Damm
2014-10-29  9:24 ` Geert Uytterhoeven
2014-10-29 23:53 ` 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=20141029235335.GB4599@verge.net.au \
    --to=horms@verge.net.au \
    --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