From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Jiri Olsa <olsajiri@gmail.com>
Cc: kernel-janitors@vger.kernel.org, ink@jurassic.park.msu.ru,
Andrew Morton <akpm@linux-foundation.org>,
rth@twiddle.net, parisc-linux@parisc-linux.org
Subject: Re: [parisc-linux] [PATCH] alpha/parisc: Removing config variable DEBUG_RWLOCK
Date: Fri, 16 Nov 2007 05:02:06 -0500 (EST) [thread overview]
Message-ID: <alpine.LFD.0.9999.0711160500080.29818@localhost.localdomain> (raw)
In-Reply-To: <473D5AAA.5020403@gmail.com>
On Fri, 16 Nov 2007, Jiri Olsa wrote:
> Robert P. J. Day wrote:
> > IIRC, you typically don't bother fixing up the defconfig files --
> > those will be regenerated eventually.
>
> I think they are part of repository... I'll check
yes, they're part of the repository but, as it was once explained to
me, they're autogenerated on a regular basis so, once there's no
remaining references to a Kconfig variable, the corresponding entries
in the defconfig files should eventually go away automatically. ergo,
don't spend any time trying to clean them up.
rday
--
========================================================================
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry
Waterloo, Ontario, CANADA
http://crashcourse.ca
========================================================================
_______________________________________________
parisc-linux mailing list
parisc-linux@lists.parisc-linux.org
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux
next prev parent reply other threads:[~2007-11-16 10:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-15 8:42 [parisc-linux] [PATCH] alpha/parisc: Removing config variable DEBUG_RWLOCK Jiri Olsa
2007-11-15 19:06 ` Grant Grundler
2007-11-15 19:54 ` Robert P. J. Day
2007-11-16 8:54 ` Jiri Olsa
2007-11-16 10:02 ` Robert P. J. Day [this message]
2007-11-16 17:32 ` Grant Grundler
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.0.9999.0711160500080.29818@localhost.localdomain \
--to=rpjday@crashcourse.ca \
--cc=akpm@linux-foundation.org \
--cc=ink@jurassic.park.msu.ru \
--cc=kernel-janitors@vger.kernel.org \
--cc=olsajiri@gmail.com \
--cc=parisc-linux@parisc-linux.org \
--cc=rth@twiddle.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