From: Ingo Molnar <mingo@elte.hu>
To: Jean Delvare <khali@linux-fr.org>
Cc: Rufus & Azrael <rufus-azrael@numericable.fr>,
Linux-kernel Mailing List <linux-kernel@vger.kernel.org>,
Takashi Iwai <tiwai@suse.de>,
Jaswinder Singh Rajput <jaswinderlinux@gmail.com>
Subject: Re: [2.6.29-rc2-git2] compilation warnings
Date: Tue, 27 Jan 2009 12:18:14 +0100 [thread overview]
Message-ID: <20090127111814.GC17848@elte.hu> (raw)
In-Reply-To: <20090127094445.010c4305@hyperion.delvare>
* Jean Delvare <khali@linux-fr.org> wrote:
> On Tue, 27 Jan 2009 08:15:29 +0100, Rufus & Azrael wrote:
> > Hi all,
>
> First of all: you really DO NOT WANT to send a message to 4000 people
> asking for an acknowledgment of receipt.
>
> > Here are my compilation warnings for fresh 2.6.29-rc2-git2 kernel :
>
> Sending 33k of warning messages at once to a generic mailing list is
> unlikely to get you anywhere. If you really want these warnings to get
> fixed, you better find the right person to report each warning.
> Otherwise your report has very little value.
Also, there's a systematic effort in tip/master to fix all build warnings
on all x86 configs that are possible to trigger (with latest GCC):
http://people.redhat.com/mingo/tip.git/README
(the new .29 warnings are not all fixed yet but work is underway)
Ingo
prev parent reply other threads:[~2009-01-27 11:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-27 7:15 [2.6.29-rc2-git2] compilation warnings Rufus & Azrael
2009-01-27 7:32 ` Takashi Iwai
2009-01-27 8:46 ` Jean Delvare
2009-01-27 9:34 ` Takashi Iwai
2009-01-27 11:16 ` Ingo Molnar
2009-01-27 11:49 ` Takashi Iwai
2009-01-27 12:48 ` Jean Delvare
2009-01-27 13:06 ` Ingo Molnar
2009-01-27 8:44 ` Jaswinder Singh Rajput
2009-01-27 8:44 ` Jean Delvare
2009-01-27 11:18 ` Ingo Molnar [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=20090127111814.GC17848@elte.hu \
--to=mingo@elte.hu \
--cc=jaswinderlinux@gmail.com \
--cc=khali@linux-fr.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rufus-azrael@numericable.fr \
--cc=tiwai@suse.de \
/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