public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: Scott Wood <scottwood@freescale•com>
To: Lijun Pan <LIJUN.PAN@FREESCALE•COM>
Cc: linuxppc-dev@ozlabs•org, Emilian.Medve@freescale•com
Subject: Re: powerpc/mpc85xx: Remove P1023 RDS support
Date: Fri, 2 May 2014 19:13:18 -0500	[thread overview]
Message-ID: <20140503001318.GA19925@home.buserror.net> (raw)
In-Reply-To: <1397841480-2652-1-git-send-email-Lijun.Pan@freescale.com>

On Fri, Apr 18, 2014 at 12:18:00PM -0500, Lijun Pan wrote:
> P1023RDS is no longer supported by Freescale while P1023RDB is still supported.

Please wrap changelogs at no more than 75 columns.

> Signed-off-by: Lijun Pan <Lijun.Pan@freescale•com>
> 
> ---
> arch/powerpc/boot/dts/p1023rds.dts                 | 219 ---------------------
>  arch/powerpc/configs/mpc85xx_defconfig             |   1 -
>  arch/powerpc/configs/mpc85xx_smp_defconfig         |   1 -
>  arch/powerpc/platforms/85xx/Kconfig                |   6 +-
>  arch/powerpc/platforms/85xx/Makefile               |   2 +-
>  .../platforms/85xx/{p1023_rds.c => p1023_rdb.c}    |  36 +---
>  6 files changed, 10 insertions(+), 255 deletions(-)
>  delete mode 100644 arch/powerpc/boot/dts/p1023rds.dts
>  rename arch/powerpc/platforms/85xx/{p1023_rds.c => p1023_rdb.c} (75%)

As discussed internally, I'd like to see more of an explanation for why
it should be removed upstream -- what sort of maintenance burden it's
causing, or why this board should be considered of so little interest to
users that we should remove it regardless of current maintenance burden.

-Scott

  reply	other threads:[~2014-05-03  0:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-18 17:18 [PATCH] powerpc/mpc85xx: Remove P1023 RDS support Lijun Pan
2014-05-03  0:13 ` Scott Wood [this message]
2014-05-03  6:44   ` Emil Medve

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=20140503001318.GA19925@home.buserror.net \
    --to=scottwood@freescale$(echo .)com \
    --cc=Emilian.Medve@freescale$(echo .)com \
    --cc=LIJUN.PAN@FREESCALE$(echo .)COM \
    --cc=linuxppc-dev@ozlabs$(echo .)org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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