linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Christophe Leroy <christophe.leroy@c-s.fr>
To: Daniel Walker <danielwa@cisco.com>,
	Andrew Morton <akpm@linux-foundation.org>
Cc: linuxppc-dev@lists.ozlabs.org, Paul Mackerras <paulus@samba.org>
Subject: Re: [PULL REQUEST] powerpc generic command line
Date: Mon, 4 Mar 2019 14:55:08 +0100	[thread overview]
Message-ID: <e80b18e3-92fe-3726-a7d7-72f98cdd0b86@c-s.fr> (raw)
In-Reply-To: <1551469472-53043-1-git-send-email-danielwa@cisco.com>



Le 01/03/2019 à 20:44, Daniel Walker a écrit :
> Here are the generic command line changes for powerpc.
> 
> These changes have been in linux-next for two cycles, with few problems reported.
> It's also been used at Cisco Systems, Inc. in production products for many many
> years with no problems.
> 
> Please pull these changes.
> 
> 
> The following changes since commit ccda4af0f4b92f7b4c308d3acc262f4a7e3affad:
> 
>    Linux 4.20-rc2 (2018-11-11 17:12:31 -0600)
> 
> are available in the git repository at:
> 
>    https://github.com/daniel-walker/cisco-linux.git for-powerpc
> 
> for you to fetch changes up to 5d4514a9c291ecf19b0626695161673d35e5d549:
> 
>    powerpc: convert config files to generic cmdline (2018-11-16 07:32:26 -0800)
> 
> ----------------------------------------------------------------
> Daniel Walker (3):
>        add generic builtin command line
>        powerpc: convert to generic builtin command line
>        powerpc: convert config files to generic cmdline

Hello,

This series is in total contradiction with the work being done to add 
KASAN support to powerpc.

It also modifies the behaviour for powerpc.

Please do not apply this series as is, see my comments on the individual 
patchs for details.

Thanks
Christophe

> 
>   arch/powerpc/Kconfig                          | 23 +--------
>   arch/powerpc/configs/44x/fsp2_defconfig       | 29 ++++++-----
>   arch/powerpc/configs/44x/iss476-smp_defconfig | 24 ++++-----
>   arch/powerpc/configs/44x/warp_defconfig       | 12 ++---
>   arch/powerpc/configs/holly_defconfig          | 12 ++---
>   arch/powerpc/configs/mvme5100_defconfig       | 25 +++++-----
>   arch/powerpc/configs/skiroot_defconfig        | 48 +++++++++---------
>   arch/powerpc/configs/storcenter_defconfig     | 15 +++---
>   arch/powerpc/kernel/prom.c                    |  4 ++
>   arch/powerpc/kernel/prom_init.c               |  8 +--
>   arch/powerpc/kernel/prom_init_check.sh        |  2 +-
>   include/linux/cmdline.h                       | 72 +++++++++++++++++++++++++++
>   init/Kconfig                                  | 69 +++++++++++++++++++++++++
>   13 files changed, 231 insertions(+), 112 deletions(-)
>   create mode 100644 include/linux/cmdline.h
> 

  reply	other threads:[~2019-03-04 13:57 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-01 19:44 [PULL REQUEST] powerpc generic command line Daniel Walker
2019-03-04 13:55 ` Christophe Leroy [this message]
2019-03-04 16:57   ` Daniel Walker
2019-03-04 17:29     ` Christophe Leroy
2019-03-04 18:11       ` Daniel Walker
2019-03-19  1:18 ` Michael Ellerman
2019-03-19 15:38   ` Daniel Walker
2019-03-19 17:42     ` Christophe Leroy
2019-03-19 18:00       ` Daniel Walker

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=e80b18e3-92fe-3726-a7d7-72f98cdd0b86@c-s.fr \
    --to=christophe.leroy@c-s.fr \
    --cc=akpm@linux-foundation.org \
    --cc=danielwa@cisco.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=paulus@samba.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).