All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: Masami Hiramatsu <masami.hiramatsu@linaro.org>
Cc: "Sugaya, Taichi" <sugaya.taichi@socionext.com>,
	Shinji Kanematsu <kanematsu.shinji@socionext.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Jassi Brar <jaswinder.singh@linaro.org>,
	soc@kernel.org, Takao Orito <orito.takao@socionext.com>,
	Kazuhiro Kasai <kasai.kazuhiro@socionext.com>,
	Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v3 9/9] ARM: configs: Add Milbeaut M10V defconfig
Date: Wed, 20 Feb 2019 14:18:31 +0100	[thread overview]
Message-ID: <CAK8P3a3DmKjTNXo8ufExaQxEsQX=MAYymeARbEzu8QXsCJFfiA@mail.gmail.com> (raw)
In-Reply-To: <CAA93ih2t34qwVB==LoF2odOCEOd9EE06i3hz0eTuonnXjJCyDw@mail.gmail.com>

On Wed, Feb 20, 2019 at 2:16 PM Masami Hiramatsu
<masami.hiramatsu@linaro.org> wrote:
> 2019年2月20日(水) 21:28 Arnd Bergmann <arnd@arndb.de>:
> > On Wed, Feb 20, 2019 at 12:27 PM Sugaya, Taichi
> > <sugaya.taichi@socionext.com> wrote:
> > > On 2019/02/20 18:28, Arnd Bergmann wrote:
> > > > On Wed, Feb 20, 2019 at 8:44 AM Sugaya Taichi
> > > > <sugaya.taichi@socionext.com> wrote:
> > > >
> > > >> diff --git a/arch/arm/configs/milbeaut_m10v_defconfig b/arch/arm/configs/milbeaut_m10v_defconfig
> > > >> new file mode 100644
> > > >> index 0000000..a263211
> > > >> --- /dev/null
> > > >> +++ b/arch/arm/configs/milbeaut_m10v_defconfig
> > > >> @@ -0,0 +1,175 @@
> > > >
> > > > I no longer see anything here that should be turned off, but you
> > > > might want to run 'make savedefconfig' and use the output of that,
> > > > to make it easier to keep it up to date.
> > > >
> > >
> > > I got it, I use the output of 'make savedefconfig'.
> > > One question, is that OK to add some options on it?
> > >   -Because "CONFIG_ARCH_MILBEAUT" was not listed.
> >
> > What I'd do here is to apply all the patches you want to get merged in
> > the next few releases before running 'savedefconfig' and use the output
> > of that.
>
> Let me check. Would you mean that the defconfig will include all those
> drivers configs, which will not appear at this moment?

Correct.

> > If you already know that you will need the options, including
> > them now means you don't have to update the defconfig file
> > as much in the future.
>
> I just concern that if other subsystem maintainer comments
> on the config name. Even in that case, can we just update the
> defconfig with new name?

Yes, that's easy enough.

      Arnd

WARNING: multiple messages have this Message-ID (diff)
From: Arnd Bergmann <arnd@arndb.de>
To: Masami Hiramatsu <masami.hiramatsu@linaro.org>
Cc: Shinji Kanematsu <kanematsu.shinji@socionext.com>,
	"Sugaya, Taichi" <sugaya.taichi@socionext.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Jassi Brar <jaswinder.singh@linaro.org>,
	soc@kernel.org, Takao Orito <orito.takao@socionext.com>,
	Kazuhiro Kasai <kasai.kazuhiro@socionext.com>,
	Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v3 9/9] ARM: configs: Add Milbeaut M10V defconfig
Date: Wed, 20 Feb 2019 14:18:31 +0100	[thread overview]
Message-ID: <CAK8P3a3DmKjTNXo8ufExaQxEsQX=MAYymeARbEzu8QXsCJFfiA@mail.gmail.com> (raw)
In-Reply-To: <CAA93ih2t34qwVB==LoF2odOCEOd9EE06i3hz0eTuonnXjJCyDw@mail.gmail.com>

On Wed, Feb 20, 2019 at 2:16 PM Masami Hiramatsu
<masami.hiramatsu@linaro.org> wrote:
> 2019年2月20日(水) 21:28 Arnd Bergmann <arnd@arndb.de>:
> > On Wed, Feb 20, 2019 at 12:27 PM Sugaya, Taichi
> > <sugaya.taichi@socionext.com> wrote:
> > > On 2019/02/20 18:28, Arnd Bergmann wrote:
> > > > On Wed, Feb 20, 2019 at 8:44 AM Sugaya Taichi
> > > > <sugaya.taichi@socionext.com> wrote:
> > > >
> > > >> diff --git a/arch/arm/configs/milbeaut_m10v_defconfig b/arch/arm/configs/milbeaut_m10v_defconfig
> > > >> new file mode 100644
> > > >> index 0000000..a263211
> > > >> --- /dev/null
> > > >> +++ b/arch/arm/configs/milbeaut_m10v_defconfig
> > > >> @@ -0,0 +1,175 @@
> > > >
> > > > I no longer see anything here that should be turned off, but you
> > > > might want to run 'make savedefconfig' and use the output of that,
> > > > to make it easier to keep it up to date.
> > > >
> > >
> > > I got it, I use the output of 'make savedefconfig'.
> > > One question, is that OK to add some options on it?
> > >   -Because "CONFIG_ARCH_MILBEAUT" was not listed.
> >
> > What I'd do here is to apply all the patches you want to get merged in
> > the next few releases before running 'savedefconfig' and use the output
> > of that.
>
> Let me check. Would you mean that the defconfig will include all those
> drivers configs, which will not appear at this moment?

Correct.

> > If you already know that you will need the options, including
> > them now means you don't have to update the defconfig file
> > as much in the future.
>
> I just concern that if other subsystem maintainer comments
> on the config name. Even in that case, can we just update the
> defconfig with new name?

Yes, that's easy enough.

      Arnd

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2019-02-20 13:18 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-20  7:45 [PATCH v3 9/9] ARM: configs: Add Milbeaut M10V defconfig Sugaya Taichi
2019-02-20  7:45 ` Sugaya Taichi
2019-02-20  9:28 ` Arnd Bergmann
2019-02-20  9:28   ` Arnd Bergmann
2019-02-20 11:27   ` Sugaya, Taichi
2019-02-20 11:27     ` Sugaya, Taichi
2019-02-20 12:27     ` Arnd Bergmann
2019-02-20 12:27       ` Arnd Bergmann
2019-02-20 13:16       ` Masami Hiramatsu
2019-02-20 13:16         ` Masami Hiramatsu
2019-02-20 13:18         ` Arnd Bergmann [this message]
2019-02-20 13:18           ` Arnd Bergmann
2019-02-20 13:23           ` Masami Hiramatsu
2019-02-20 13:23             ` Masami Hiramatsu
2019-02-21  0:36             ` Sugaya, Taichi
2019-02-21  0:36               ` Sugaya, Taichi

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='CAK8P3a3DmKjTNXo8ufExaQxEsQX=MAYymeARbEzu8QXsCJFfiA@mail.gmail.com' \
    --to=arnd@arndb.de \
    --cc=jaswinder.singh@linaro.org \
    --cc=kanematsu.shinji@socionext.com \
    --cc=kasai.kazuhiro@socionext.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=masami.hiramatsu@linaro.org \
    --cc=orito.takao@socionext.com \
    --cc=soc@kernel.org \
    --cc=sugaya.taichi@socionext.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.