All of lore.kernel.org
 help / color / mirror / Atom feed
From: Masahiro Yamada <yamada.masahiro@socionext.com>
To: Christoph Hellwig <hch@lst.de>
Cc: Randy Dunlap <rdunlap@infradead.org>,
	Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/5] Kconfig: consolidate the "Kernel hacking menu"
Date: Thu, 5 Jul 2018 14:40:15 +0900	[thread overview]
Message-ID: <CAK7LNAT-hR1OtB4K53EeYoJEXY6kP8OjpFDt6Kpasw2fzQKPYw@mail.gmail.com> (raw)
In-Reply-To: <20180702144711.22111-3-hch@lst.de>

2018-07-02 23:47 GMT+09:00 Christoph Hellwig <hch@lst.de>:
> Move the source of lib/Kconfig.debug and arch/$(ARCH)/Kconfig.debug to
> the top-level Kconfig.  For two architectures that means moving their
> arch-specific symbols in that menu into a new arch Kconfig.debug file,
> and for a few more creating a dummy file so that we can include it
> unconditionally.
>
> Also move the actual 'Kernel hacking' menu to lib/Kconfig.debug, where
> it belongs.
>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
> ---




> diff --git a/arch/c6x/Kconfig.debug b/arch/c6x/Kconfig.debug
> new file mode 100644
> index 000000000000..49edf08813eb
> --- /dev/null
> +++ b/arch/c6x/Kconfig.debug
> @@ -0,0 +1,11 @@
> +# SPDX-License-Identifier: GPL-2.0
> +
> +config ACCESS_CHECK
> +       bool "Check the user pointer address"
> +       default y
> +       help
> +         Usually the pointer transfer from user space is checked to see if its
> +         address is in the kernel space.
> +
> +         Say N here to disable that check to improve the performance.
> +

Just a nit:

When I ran 'git am', it complained about a blank line at the end of file.

.git/rebase-apply/patch:229: new blank line at EOF.






-- 
Best Regards
Masahiro Yamada

  parent reply	other threads:[~2018-07-05  5:41 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-02 14:47 include architecture Kconfig files from top-level Kconfig Christoph Hellwig
2018-07-02 14:47 ` [PATCH 1/5] kconfig: include common " Christoph Hellwig
2018-07-02 20:03   ` Randy Dunlap
2018-07-02 20:08     ` Randy Dunlap
2018-07-03 13:36       ` Christoph Hellwig
2018-07-03 16:11         ` Randy Dunlap
2018-07-05  5:38           ` Masahiro Yamada
2018-07-03 13:35     ` Christoph Hellwig
2018-07-02 20:41   ` Randy Dunlap
2018-07-02 20:50     ` Randy Dunlap
2018-07-05  6:04       ` Masahiro Yamada
2018-07-02 14:47 ` [PATCH 2/5] Kconfig: consolidate the "Kernel hacking menu" Christoph Hellwig
2018-07-02 20:28   ` Randy Dunlap
2018-07-05  5:40   ` Masahiro Yamada [this message]
2018-07-02 14:47 ` [PATCH 3/5] kconfig: include kernel/Kconfig.preempt from top-level Kconfig Christoph Hellwig
2018-07-02 22:02   ` [PATCH] Kconfig: menus: add PREEMPT options back Randy Dunlap
2018-07-02 14:47 ` [PATCH 4/5] kconfig: add a Memory Management options" menu Christoph Hellwig
2018-07-02 20:57   ` Randy Dunlap
2018-07-02 14:47 ` [PATCH 5/5] kconfig: move the "Executable file formats" menu to fs/Kconfig.binfmt Christoph Hellwig
2018-07-02 20:58   ` Randy Dunlap
2018-07-02 21:17 ` [PATCH] arch/Kconfig: use a menu to reduce clutter Randy Dunlap
2018-07-03 13:39   ` Christoph Hellwig
2018-07-03 13:40     ` Christoph Hellwig
2018-07-05  5:47 ` include architecture Kconfig files from top-level Kconfig Masahiro Yamada

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=CAK7LNAT-hR1OtB4K53EeYoJEXY6kP8OjpFDt6Kpasw2fzQKPYw@mail.gmail.com \
    --to=yamada.masahiro@socionext.com \
    --cc=hch@lst.de \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@infradead.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 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.