All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Soeren Sonnenburg <kernel@nn7.de>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.25-git-current several Section mismatch in reference from ...
Date: Sat, 23 Feb 2008 09:00:29 +0100	[thread overview]
Message-ID: <20080223080029.GA11684@uranus.ravnborg.org> (raw)
In-Reply-To: <1203752993.4498.4.camel@localhost>

On Sat, Feb 23, 2008 at 08:49:53AM +0100, Soeren Sonnenburg wrote:
> compiling with
> 
> make CONFIG_DEBUG_SECTION_MISMATCH=y
> 
> I see the following warnings:
> 
>   CC      kernel/stacktrace.o
>   CC      kernel/irq/handle.o
>   LD      mm/built-in.o


Hi Sören.

>From a quick scan I would say most if not all of the
section mismatch warnings are dealt with. The patches
are queued for next -mm and some may be forwarded to
mainline before the release.

Patchset was posted by me last weeken to lkml so they
should be fairly easy to find.

	Sam

      reply	other threads:[~2008-02-23  8:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-23  7:49 2.6.25-git-current several Section mismatch in reference from Soeren Sonnenburg
2008-02-23  8:00 ` 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=20080223080029.GA11684@uranus.ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=kernel@nn7.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.