public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Randy Dunlap <rdunlap@xenotime.net>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: still worth running kernel cleanup scripts after merge windows?
Date: Tue, 9 Mar 2010 06:20:58 -0500 (EST)	[thread overview]
Message-ID: <alpine.LFD.2.00.1003090620080.3972@localhost> (raw)
In-Reply-To: <4B9585A7.908@xenotime.net>

On Mon, 8 Mar 2010, Randy Dunlap wrote:

> On 03/08/10 05:07, Robert P. J. Day wrote:

> >   as a single example, here's a snippet from the
> > drivers/message/fusion directory, identifying an apparently bad
> > reference to a non-existent CONFIG variable:
> >
> >>>>>> FUSION_MAX_FC_SGE
> > drivers/message/fusion/mptbase.h:179:#ifdef CONFIG_FUSION_MAX_FC_SGE
> > drivers/message/fusion/mptbase.h:180:#if CONFIG_FUSION_MAX_FC_SGE  < 16
> > drivers/message/fusion/mptbase.h:182:#elif CONFIG_FUSION_MAX_FC_SGE  > 256
> > drivers/message/fusion/mptbase.h:185:#define MPT_SCSI_FC_SG_DEPTH  CONFIG_FUSION_MAX_FC_SGE
> >
> >   but there is no such Kconfig variable FUSION_MAX_FC_SGE.  however:
> >
> > $ grep -r FUSION_MAX drivers/message/fusion
> > drivers/message/fusion/Kconfig:config FUSION_MAX_SGE
> > drivers/message/fusion/mptbase.h:#ifdef CONFIG_FUSION_MAX_SGE
> > drivers/message/fusion/mptbase.h:#if CONFIG_FUSION_MAX_SGE  < 16
> > drivers/message/fusion/mptbase.h:#elif CONFIG_FUSION_MAX_SGE  > 128
> > drivers/message/fusion/mptbase.h:#define MPT_SCSI_SG_DEPTH	CONFIG_FUSION_MAX_SGE
> > drivers/message/fusion/mptbase.h:#ifdef CONFIG_FUSION_MAX_FC_SGE
> > drivers/message/fusion/mptbase.h:#if CONFIG_FUSION_MAX_FC_SGE  < 16
> > drivers/message/fusion/mptbase.h:#elif CONFIG_FUSION_MAX_FC_SGE  > 256
> > drivers/message/fusion/mptbase.h:#define MPT_SCSI_FC_SG_DEPTH	CONFIG_FUSION_MAX_FC_SGE
> > $
> >
> >   so is that a typo?  should "FUSION_MAX_FC_SGE" really be just
> > "FUSION_MAX_SGE"?  anyway, you get the idea.  or maybe i should just
> > put the scripts up at my wiki and people can run their at their
> > leisure on whatever part of the source tree interests them.
>
> Yes, please.

http://www.crashcourse.ca/wiki/index.php/Kernel_cleanup_scripts

have fun.  (only the first script is there at the moment, additional
scripts to appear shortly.)

rday
--



========================================================================
Robert P. J. Day                               Waterloo, Ontario, CANADA

            Linux Consulting, Training and Kernel Pedantry.

Web page:                                          http://crashcourse.ca
Twitter:                                       http://twitter.com/rpjday
========================================================================

      reply	other threads:[~2010-03-09 11:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-08 13:07 still worth running kernel cleanup scripts after merge windows? Robert P. J. Day
2010-03-08 23:17 ` Randy Dunlap
2010-03-09 11:20   ` Robert P. J. Day [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=alpine.LFD.2.00.1003090620080.3972@localhost \
    --to=rpjday@crashcourse.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@xenotime.net \
    /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