public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Chris Wright <chrisw@sous-sol.org>
Cc: Bart Van Assche <bart.vanassche@gmail.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Greg Kroah-Hartman <greg@kroah.com>,
	rufus-azrael@numericable.fr
Subject: Re: 2.6.25 section mismatches
Date: Thu, 17 Apr 2008 19:44:40 +0200	[thread overview]
Message-ID: <20080417174440.GA14864@uranus.ravnborg.org> (raw)
In-Reply-To: <20080417170149.GC17220@sequoia.sous-sol.org>

On Thu, Apr 17, 2008 at 10:01:49AM -0700, Chris Wright wrote:
> * Bart Van Assche (bart.vanassche@gmail.com) wrote:
> > On Thu, Apr 17, 2008 at 11:46 AM, Bart Van Assche
> > <bart.vanassche@gmail.com> wrote:
> > > Apparently there is a significant number of section mismatches in the
> > >  2.6.25 kernel. These were already reported against 2.6.25-rc1 and are
> > >  still present in the final 2.6.25 release. These section mismatches
> > >  show up at least on the i386 and x86_64 architectures. Maybe it's a
> > >  good idea before a patch is merged not only to check whether the patch
> > >  applies cleanly but also to check whether it doesn't create any new
> > >  section mismatches ?
> > >
> > >  See also http://bugzilla.kernel.org/show_bug.cgi?id=9974.
> > 
> > Who should look into this ?
> 
> Sam, any of these look familiar (or put another way...are there still
> outstanding section mismatch fixes in -mm)?

>From a quick scan I will say that at least half of these have pending fixes in -mm.
I'm looking forward to see where we are after Andrew's first merge.

	Sam

      reply	other threads:[~2008-04-17 17:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-17  9:46 2.6.25 section mismatches Bart Van Assche
2008-04-17 16:49 ` Bart Van Assche
2008-04-17 17:01   ` Chris Wright
2008-04-17 17:44     ` 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=20080417174440.GA14864@uranus.ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=bart.vanassche@gmail.com \
    --cc=chrisw@sous-sol.org \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rufus-azrael@numericable.fr \
    /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