All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Weinberger <richard@nod.at>
To: Christoph Hellwig <hch@lst.de>
Cc: Masahiro Yamada <yamada.masahiro@socionext.com>,
	Randy Dunlap <rdunlap@infradead.org>,
	linux-kbuild@vger.kernel.org, linux-um@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: include architecture Kconfig files from top-level Kconfig v2
Date: Mon, 23 Jul 2018 12:46:51 +0200	[thread overview]
Message-ID: <8939171.tHQiqpY3WF@blindfold> (raw)
In-Reply-To: <20180708152004.21679-1-hch@lst.de>

Am Sonntag, 8. Juli 2018, 17:19:55 CEST schrieb Christoph Hellwig:
> Hi Masahiro,
> 
> what do you think about the series below, which moves the includes
> of all the architecture independ Kconfig files to the top-level
> Kconfig instead of duplicating the includes in all architectures?
> 
> Note that this only handles the low-hanging fruite, there are a lot
> of other bits that should probably be cleaned up to be common,
> but those will be not entirely trivial.
> 
> Changes since v1:
>  - add back a remove source statement from arch/arm/Kconfig
>  - various fixes from Randy
>  - various UML patches to be able to use the common Kconfig

For the UML bits,

Acked-by: Richard Weinberger <richard@nod.at>

Thanks,
//richard


WARNING: multiple messages have this Message-ID (diff)
From: Richard Weinberger <richard@nod.at>
To: Christoph Hellwig <hch@lst.de>
Cc: Masahiro Yamada <yamada.masahiro@socionext.com>,
	Randy Dunlap <rdunlap@infradead.org>,
	linux-um@lists.infradead.org, linux-kernel@vger.kernel.org,
	linux-kbuild@vger.kernel.org
Subject: Re: include architecture Kconfig files from top-level Kconfig v2
Date: Mon, 23 Jul 2018 12:46:51 +0200	[thread overview]
Message-ID: <8939171.tHQiqpY3WF@blindfold> (raw)
In-Reply-To: <20180708152004.21679-1-hch@lst.de>

Am Sonntag, 8. Juli 2018, 17:19:55 CEST schrieb Christoph Hellwig:
> Hi Masahiro,
> 
> what do you think about the series below, which moves the includes
> of all the architecture independ Kconfig files to the top-level
> Kconfig instead of duplicating the includes in all architectures?
> 
> Note that this only handles the low-hanging fruite, there are a lot
> of other bits that should probably be cleaned up to be common,
> but those will be not entirely trivial.
> 
> Changes since v1:
>  - add back a remove source statement from arch/arm/Kconfig
>  - various fixes from Randy
>  - various UML patches to be able to use the common Kconfig

For the UML bits,

Acked-by: Richard Weinberger <richard@nod.at>

Thanks,
//richard


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


  parent reply	other threads:[~2018-07-23 10:47 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-08 15:19 include architecture Kconfig files from top-level Kconfig v2 Christoph Hellwig
2018-07-08 15:19 ` Christoph Hellwig
2018-07-08 15:19 ` [PATCH 1/9] um: stop abusing KBUILD_KCONFIG Christoph Hellwig
2018-07-08 15:19   ` Christoph Hellwig
2018-07-08 15:19 ` [PATCH 2/9] um: cleanup Kconfig files Christoph Hellwig
2018-07-08 15:19 ` [PATCH 3/9] um: create a proper drivers Kconfig Christoph Hellwig
2018-07-08 15:19   ` Christoph Hellwig
2018-07-08 15:19 ` [PATCH 4/9] kconfig: include common Kconfig files from top-level Kconfig Christoph Hellwig
2018-07-08 15:19   ` Christoph Hellwig
2018-07-11 12:21   ` Masahiro Yamada
2018-07-11 12:21     ` Masahiro Yamada
2018-07-17  6:33     ` Randy Dunlap
2018-07-17  6:33       ` Randy Dunlap
2018-07-17  6:42       ` Randy Dunlap
2018-07-17  6:42         ` Randy Dunlap
2018-07-17  6:44         ` Randy Dunlap
2018-07-17  6:44           ` Randy Dunlap
2018-07-17  6:55           ` Randy Dunlap
2018-07-17  6:55             ` Randy Dunlap
2018-07-17 13:00         ` Christoph Hellwig
2018-07-17 13:00           ` Christoph Hellwig
2018-07-17 12:59       ` Christoph Hellwig
2018-07-17 12:59         ` Christoph Hellwig
2018-07-18  7:06     ` Randy Dunlap
2018-07-18  7:06       ` Randy Dunlap
2018-07-19 13:11       ` Christoph Hellwig
2018-07-19 13:11         ` Christoph Hellwig
2018-07-20 19:57         ` Dirk Gouders
2018-07-20 19:57           ` Dirk Gouders
2018-07-08 15:20 ` [PATCH 5/9] Kconfig: consolidate the "Kernel hacking" menu Christoph Hellwig
2018-07-08 15:20   ` Christoph Hellwig
2018-07-08 16:34   ` Randy Dunlap
2018-07-08 16:34     ` Randy Dunlap
2018-07-08 15:20 ` [PATCH 6/9] kconfig: include kernel/Kconfig.preempt from init/Kconfig Christoph Hellwig
2018-07-08 15:20   ` Christoph Hellwig
2018-07-08 16:30   ` Randy Dunlap
2018-07-08 16:30     ` Randy Dunlap
2018-07-08 15:20 ` [PATCH 7/9] arch/Kconfig: use a menu to reduce clutter Christoph Hellwig
2018-07-08 15:20   ` Christoph Hellwig
2018-07-08 15:20 ` [PATCH 8/9] kconfig: move the "Executable file formats" menu to fs/Kconfig.binfmt Christoph Hellwig
2018-07-08 15:20   ` Christoph Hellwig
2018-07-08 15:20 ` [PATCH 9/9] kconfig: add a Memory Management options" menu Christoph Hellwig
2018-07-08 15:20   ` Christoph Hellwig
2018-07-23 10:46 ` Richard Weinberger [this message]
2018-07-23 10:46   ` include architecture Kconfig files from top-level Kconfig v2 Richard Weinberger

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=8939171.tHQiqpY3WF@blindfold \
    --to=richard@nod.at \
    --cc=hch@lst.de \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-um@lists.infradead.org \
    --cc=rdunlap@infradead.org \
    --cc=yamada.masahiro@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.