From: Sam Ravnborg <sam@ravnborg.org>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Section mismatch warnings
Date: Sat, 24 Jun 2006 00:12:18 +0200 [thread overview]
Message-ID: <20060623221217.GA372@mars.ravnborg.org> (raw)
In-Reply-To: <Pine.LNX.4.61.0606231938080.26864@yvahk01.tjqt.qr>
On Fri, Jun 23, 2006 at 07:40:12PM +0200, Jan Engelhardt wrote:
> Hello,
>
>
> as others have already seen to, 2.6.17 spits out a lot of section mismatch
> warnings on modpost. Some of them have may already been addressed; here is
> the output I get when MODPOST starts to run during the compile process of
> an almost-completely-compiled kernel. Need .config?
All the .smp_locks related warnings are gone when I get the kbuild.git
tree pushed linus wise. Needs to spend only an hour or so before it is
ready and will do so during the weekend.
Sam
next prev parent reply other threads:[~2006-06-23 22:13 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-23 17:40 Section mismatch warnings Jan Engelhardt
2006-06-23 22:12 ` Sam Ravnborg [this message]
2006-06-23 22:22 ` Al Viro
2006-06-24 21:02 ` Sam Ravnborg
2006-06-23 22:23 ` Al Viro
2006-06-26 12:37 ` Roman Zippel
-- strict thread matches above, loose matches on Subject: below --
2007-07-30 17:48 Gabriel C
2007-07-30 18:51 ` Sam Ravnborg
2007-07-30 19:31 ` Gabriel C
2007-07-31 19:45 ` Gabriel C
2007-07-31 20:48 ` Sam Ravnborg
2007-07-31 21:58 ` Gabriel C
2007-08-02 14:27 ` Gabriel C
2007-08-02 16:31 ` Sam Ravnborg
2007-08-02 17:12 ` Gabriel C
2007-08-02 17:59 ` Sam Ravnborg
2007-08-02 18:24 ` Gabriel C
2014-10-06 18:42 section " Michael Hu (NSBU)
[not found] ` <D058300A.10185%humichael-pghWNbHTmq7QT0dZR+AlfA@public.gmane.org>
2014-10-07 14:31 ` Sergio Gonzalez Monroy
2014-10-07 16:46 ` Neil Horman
[not found] ` <20141007164635.GC27719-B26myB8xz7F8NnZeBjwnZQMhkBWG/bsMQH7oEaQurus@public.gmane.org>
2014-10-08 21:34 ` Michael Hu (NSBU)
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=20060623221217.GA372@mars.ravnborg.org \
--to=sam@ravnborg.org \
--cc=jengelh@linux01.gwdg.de \
--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 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.