From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: NeilBrown <neilb@suse.com>
Cc: James Simmons <jsimmons@infradead.org>,
Oleg Drokin <oleg.drokin@intel.com>,
Andreas Dilger <andreas.dilger@intel.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Lustre Development List <lustre-devel@lists.lustre.org>
Subject: [lustre-devel] [PATCH 1/6] staging: lustre: move stack-check macros to libcfs_debug.h
Date: Mon, 23 Apr 2018 15:03:17 +0200 [thread overview]
Message-ID: <20180423130317.GA17153@kroah.com> (raw)
In-Reply-To: <87a7u1s1fi.fsf@notabene.neil.brown.name>
On Wed, Apr 18, 2018 at 12:17:37PM +1000, NeilBrown wrote:
> On Mon, Apr 16 2018, James Simmons wrote:
>
> >> CDEBUG_STACK() and CHECK_STACK() are macros to help with
> >> debugging, so move them from
> >> drivers/staging/lustre/include/linux/libcfs/linux/libcfs.h
> >> to
> >> drivers/staging/lustre/include/linux/libcfs/libcfs_debug.h
> >>
> >> This seems a more fitting location, and is a step towards
> >> removing linux/libcfs.h and simplifying the include file structure.
> >
> > Nak. Currently the lustre client always enables debugging but that
> > shouldn't be the case. What we do need is the able to turn off the
> > crazy debugging stuff. In the development branch of lustre it is
> > done with CDEBUG_ENABLED. We need something like that in Kconfig
> > much like we have CONFIG_LUSTRE_DEBUG_EXPENSIVE_CHECK. Since we like
> > to be able to turn that off this should be moved to just after
> > LIBCFS_DEBUG_MSG_DATA_DECL. Then from CHECK_STACK down to CWARN()
> > it can be build out. When CDEBUG_ENABLED is disabled CDEBUG_LIMIT
> > would be empty.
>
> So why, exactly, is this an argument to justify a NAK?
> Are you just saying that the code I moved into libcfs_debug.h should be
> moved to somewhere a bit later in the file?
> That can easily be done when it is needed. It isn't needed now so why
> insist on it?
>
> Each patch should do one thing and make clear forward progress. This
> patch gets rid of an unnecessary file and brings related code together.
> I think that qualifies.
I agree, this just deletes an unused file, it changes no functionality
at all. Now applied.
greg k-h
WARNING: multiple messages have this Message-ID (diff)
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: NeilBrown <neilb@suse.com>
Cc: James Simmons <jsimmons@infradead.org>,
Oleg Drokin <oleg.drokin@intel.com>,
Andreas Dilger <andreas.dilger@intel.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Lustre Development List <lustre-devel@lists.lustre.org>
Subject: Re: [PATCH 1/6] staging: lustre: move stack-check macros to libcfs_debug.h
Date: Mon, 23 Apr 2018 15:03:17 +0200 [thread overview]
Message-ID: <20180423130317.GA17153@kroah.com> (raw)
In-Reply-To: <87a7u1s1fi.fsf@notabene.neil.brown.name>
On Wed, Apr 18, 2018 at 12:17:37PM +1000, NeilBrown wrote:
> On Mon, Apr 16 2018, James Simmons wrote:
>
> >> CDEBUG_STACK() and CHECK_STACK() are macros to help with
> >> debugging, so move them from
> >> drivers/staging/lustre/include/linux/libcfs/linux/libcfs.h
> >> to
> >> drivers/staging/lustre/include/linux/libcfs/libcfs_debug.h
> >>
> >> This seems a more fitting location, and is a step towards
> >> removing linux/libcfs.h and simplifying the include file structure.
> >
> > Nak. Currently the lustre client always enables debugging but that
> > shouldn't be the case. What we do need is the able to turn off the
> > crazy debugging stuff. In the development branch of lustre it is
> > done with CDEBUG_ENABLED. We need something like that in Kconfig
> > much like we have CONFIG_LUSTRE_DEBUG_EXPENSIVE_CHECK. Since we like
> > to be able to turn that off this should be moved to just after
> > LIBCFS_DEBUG_MSG_DATA_DECL. Then from CHECK_STACK down to CWARN()
> > it can be build out. When CDEBUG_ENABLED is disabled CDEBUG_LIMIT
> > would be empty.
>
> So why, exactly, is this an argument to justify a NAK?
> Are you just saying that the code I moved into libcfs_debug.h should be
> moved to somewhere a bit later in the file?
> That can easily be done when it is needed. It isn't needed now so why
> insist on it?
>
> Each patch should do one thing and make clear forward progress. This
> patch gets rid of an unnecessary file and brings related code together.
> I think that qualifies.
I agree, this just deletes an unused file, it changes no functionality
at all. Now applied.
greg k-h
next prev parent reply other threads:[~2018-04-23 13:03 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-16 0:42 [lustre-devel] [PATCH 0/6] staging: lustre: code rearrangement NeilBrown
2018-04-16 0:42 ` NeilBrown
2018-04-16 0:42 ` [lustre-devel] [PATCH 1/6] staging: lustre: move stack-check macros to libcfs_debug.h NeilBrown
2018-04-16 0:42 ` NeilBrown
2018-04-16 3:48 ` [lustre-devel] " James Simmons
2018-04-16 3:48 ` James Simmons
2018-04-16 15:27 ` [lustre-devel] " Patrick Farrell
2018-04-16 15:27 ` Patrick Farrell
2018-04-16 22:42 ` James Simmons
2018-04-16 22:42 ` James Simmons
2018-04-16 22:48 ` Doug Oucharek
2018-04-16 22:48 ` Doug Oucharek
2018-04-17 5:26 ` Dilger, Andreas
2018-04-17 5:26 ` Dilger, Andreas
2018-04-17 15:41 ` Doug Oucharek
2018-04-17 15:41 ` Doug Oucharek
2018-04-18 2:29 ` NeilBrown
2018-04-18 2:29 ` NeilBrown
2018-04-18 4:23 ` Patrick Farrell
2018-04-18 4:23 ` Patrick Farrell
2018-04-18 2:17 ` NeilBrown
2018-04-18 2:17 ` NeilBrown
2018-04-23 13:03 ` Greg Kroah-Hartman [this message]
2018-04-23 13:03 ` Greg Kroah-Hartman
2018-04-16 0:42 ` [lustre-devel] [PATCH 6/6] staging: lustre: move remaining code from linux-module.c to module.c NeilBrown
2018-04-16 0:42 ` NeilBrown
2018-04-16 0:42 ` [lustre-devel] [PATCH 5/6] staging: lustre: move misc-device registration closer to related code NeilBrown
2018-04-16 0:42 ` NeilBrown
2018-04-23 13:12 ` [lustre-devel] " Greg Kroah-Hartman
2018-04-23 13:12 ` Greg Kroah-Hartman
2018-04-16 0:42 ` [lustre-devel] [PATCH 2/6] staging: lustre: remove libcfs/linux/libcfs.h NeilBrown
2018-04-16 0:42 ` NeilBrown
2018-04-16 3:35 ` [lustre-devel] " James Simmons
2018-04-16 3:35 ` James Simmons
2018-04-18 2:32 ` [lustre-devel] " NeilBrown
2018-04-18 2:32 ` NeilBrown
2018-04-23 13:03 ` [lustre-devel] " Greg Kroah-Hartman
2018-04-23 13:03 ` Greg Kroah-Hartman
2018-04-16 0:42 ` [lustre-devel] [PATCH 3/6] staging: lustre: remove include/linux/libcfs/linux/linux-cpu.h NeilBrown
2018-04-16 0:42 ` NeilBrown
2018-04-16 3:52 ` [lustre-devel] " James Simmons
2018-04-16 3:52 ` James Simmons
2018-04-18 2:33 ` [lustre-devel] " NeilBrown
2018-04-18 2:33 ` NeilBrown
2018-04-23 13:13 ` [lustre-devel] " Greg Kroah-Hartman
2018-04-23 13:13 ` Greg Kroah-Hartman
2018-04-16 0:42 ` [lustre-devel] [PATCH 4/6] staging: lustre: rearrange placement of CPU partition management code NeilBrown
2018-04-16 0:42 ` NeilBrown
2018-04-16 3:53 ` [lustre-devel] " James Simmons
2018-04-16 3:53 ` James Simmons
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=20180423130317.GA17153@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=andreas.dilger@intel.com \
--cc=jsimmons@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lustre-devel@lists.lustre.org \
--cc=neilb@suse.com \
--cc=oleg.drokin@intel.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.