public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Jeff Garzik <jeff@garzik.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	LKML <linux-kernel@vger.kernel.org>,
	linux arch <linux-arch@vger.kernel.org>,
	James Bottomley <James.Bottomley@HansenPartnership.com>
Subject: Re: Are Section mismatches out of control?
Date: Fri, 1 Feb 2008 21:17:13 +0100	[thread overview]
Message-ID: <20080201201713.GA15905@uranus.ravnborg.org> (raw)
In-Reply-To: <47A34C47.9040306@garzik.org>

> Another way to look at it...  All of a sudden, different from 2.6.24, 
> kernel 2.6.25-git build spews so many warnings that I need to disable 
> section mismatch checking completely, because there is so much noise 
> that __normal build messages scroll off the screen__.

One can ignore or one can fix...
I decided to spend some of my friday on fixing section mismatch
warnings as I've got a bit irritated over people spending time
complaining but failing to provide patches.

My work approach was to seelct a directory and fix all warnings
there before moving on. So I did not as such pick the easy ones
or anything like that.

Despite this I managed with a one day effort to bring down
the number of warnings in my build from 106 to 50 warnings.
And yesterday the figure was 136.

So when complaining about the number of warnings I can only say
that we would all benefit if they are fixed.
Just ignoring them will not sort it out.

I did not pull your latest patches so my numbers are outdated
for net/drivers/ which alone count for 11 out of 50 warnings
in my tree.

I am also eagerly awaiting Andrew to push as he has a few
patches pending all over but the section mismatch warnings
are the least of his worries these days.

I hope to get down to less than 20 warnings in my allyesconfig
build before the merge window closes.
And with just a bit of assistance from others this
is doable.

	Sam - who expected more people to actually fix this stuff :-(

  reply	other threads:[~2008-02-01 20:17 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-01 10:47 Are Section mismatches out of control? Sam Ravnborg
2008-02-01 11:03 ` Andrew Morton
2008-02-01 11:21   ` Harvey Harrison
2008-02-01 13:30     ` Geert Uytterhoeven
2008-02-01 13:40       ` Sam Ravnborg
2008-02-01 21:22         ` Geert Uytterhoeven
2008-02-01 22:32           ` Sam Ravnborg
2008-02-02 16:42             ` Geert Uytterhoeven
2008-02-02 17:40               ` Sam Ravnborg
2008-02-01 17:02     ` Roland Dreier
2008-02-01 21:47     ` Jan Engelhardt
2008-02-01 22:10       ` James Bottomley
2008-02-01 22:40       ` Sam Ravnborg
2008-02-02  0:01         ` Jan Engelhardt
2008-02-01 14:48   ` Johannes Weiner
2008-02-01 15:00   ` James Bottomley
2008-02-01 16:43   ` Jeff Garzik
2008-02-01 20:17     ` Sam Ravnborg [this message]
2008-02-01 20:24       ` Jeff Garzik
2008-02-01 22:38         ` Sam Ravnborg
2008-02-01 11:10 ` Andi Kleen
2008-02-01 21:51   ` Jan Engelhardt
2008-02-02  4:12     ` Andi Kleen
2008-02-01 14:53 ` James Bottomley

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=20080201201713.GA15905@uranus.ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=akpm@linux-foundation.org \
    --cc=jeff@garzik.org \
    --cc=linux-arch@vger.kernel.org \
    --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