From: Sam Ravnborg <sam@ravnborg.org>
To: Peter Teoh <htmldeveloper@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: CONFIG_SECTION_MISMATCH is replaced by CONFIG_DEBUG_SECTION_MISMATCH?
Date: Sat, 2 Feb 2008 18:39:01 +0100 [thread overview]
Message-ID: <20080202173901.GB24765@uranus.ravnborg.org> (raw)
In-Reply-To: <804dabb00802020820k567bf07cg780da10a0b083e6e@mail.gmail.com>
On Sun, Feb 03, 2008 at 12:20:41AM +0800, Peter Teoh wrote:
> I supposed CONFIG_SECTION_MISMATCH has been deprecated by
> CONFIG_DEBUG_SECTION_MISMATCH, as I found
> CONFIG_DEBUG_SECTION_MISMATCH in Makefile, Makefile.build and
> Makefile.modpost, but not the former symbol. Moreover, setting the
> symbol in .config, and followed by make oldconfig will result in the
> non-debug symbol disappearing, but not the debug version. Am I
> correct?
Simple error on my side.
Will fix while I touch this code for another reason.
Thanks for the report and proposed patch!
Sam
prev parent reply other threads:[~2008-02-02 17:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-02 16:20 Peter Teoh
2008-02-02 17:39 ` Sam Ravnborg [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=20080202173901.GB24765@uranus.ravnborg.org \
--to=sam@ravnborg.org \
--cc=htmldeveloper@gmail.com \
--cc=linux-kernel@vger.kernel.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 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®