mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Changbin Du <changbin.du@gmail.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Changbin Du <changbin.du@gmail.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/8] kconfig/hacking: make 'kernel hacking' menu better structured
Date: Mon, 9 Sep 2019 22:10:26 +0800	[thread overview]
Message-ID: <20190909141024.rq2pdl2vqqdmdm4m@mail.google.com> (raw)
In-Reply-To: <81a27c4e-98d4-bf6a-c81c-b85666c9a366@infradead.org>

On Sun, Sep 08, 2019 at 05:44:54PM -0700, Randy Dunlap wrote:
> On 9/7/19 6:27 PM, Changbin Du wrote:
> > This series is a trivial improvment for the layout of 'kernel hacking'
> > configuration menu. Now we have many items in it which makes takes
> > a little time to look up them since they are not well structured yet.
> > 
> > Early discussion is here:
> > https://lkml.org/lkml/2019/9/1/39
> > 
> > Changbin Du (8):
> >   kconfig/hacking: Group sysrq/kgdb/ubsan into 'Generic Kernel Debugging
> >     Instruments'
> >   kconfig/hacking: Create submenu for arch special debugging options
> >   kconfig/hacking: Group kernel data structures debugging together
> >   kconfig/hacking: Move kernel testing and coverage options to same
> >     submenu
> >   kconfig/hacking: Move Oops into 'Lockups and Hangs'
> >   kconfig/hacking: Move SCHED_STACK_END_CHECK after DEBUG_STACK_USAGE
> >   kconfig/hacking: Create a submenu for scheduler debugging options
> >   kconfig/hacking: Move DEBUG_BUGVERBOSE to 'printk and dmesg options'
> > 
> >  lib/Kconfig.debug | 627 ++++++++++++++++++++++++----------------------
> >  1 file changed, 324 insertions(+), 303 deletions(-)
> 
> Hi,
> 
> Series applies to v5.3-rc7.  Has some problems applying to linux-next.
>
Let me rebase to linux-next.

> Under 'Compile-time checks and compiler options', "Debug Filesystem" does not belong here.
> Maybe move it under 'Generic Kernel Debugging Instruments'.
> 
yes, let's move it to 'Generic Kernel Debugging Instruments'.

> I mostly like it.  I might have put 'Debug notifier call chains' under
> 'Debug kernel data structures', but that's not a big deal.
> 
no problem.

> -- 
> ~Randy

-- 
Cheers,
Changbin Du

      reply	other threads:[~2019-09-09 14:10 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-08  1:27 Changbin Du
2019-09-08  1:27 ` [PATCH 1/8] kconfig/hacking: Group sysrq/kgdb/ubsan into 'Generic Kernel Debugging Instruments' Changbin Du
2019-09-08  1:27 ` [PATCH 2/8] kconfig/hacking: Create submenu for arch special debugging options Changbin Du
2019-09-08  1:27 ` [PATCH 3/8] kconfig/hacking: Group kernel data structures debugging together Changbin Du
2019-09-08  1:27 ` [PATCH 4/8] kconfig/hacking: Move kernel testing and coverage options to same submenu Changbin Du
2019-09-08  1:27 ` [PATCH 5/8] kconfig/hacking: Move Oops into 'Lockups and Hangs' Changbin Du
2019-09-08  1:27 ` [PATCH 6/8] kconfig/hacking: Move SCHED_STACK_END_CHECK after DEBUG_STACK_USAGE Changbin Du
2019-09-08  1:27 ` [PATCH 7/8] kconfig/hacking: Create a submenu for scheduler debugging options Changbin Du
2019-09-08  1:28 ` [PATCH 8/8] kconfig/hacking: Move DEBUG_BUGVERBOSE to 'printk and dmesg options' Changbin Du
2019-09-08  1:30 ` [PATCH 0/8] kconfig/hacking: make 'kernel hacking' menu better structured Changbin Du
2019-09-09  0:44 ` Randy Dunlap
2019-09-09 14:10   ` Changbin Du [this message]

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=20190909141024.rq2pdl2vqqdmdm4m@mail.google.com \
    --to=changbin.du@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@infradead.org \
    --cc=tglx@linutronix.de \
    /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

all inboxes | Powered by JetHome®