linux-arch.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jarek Poplawski <jarkao2@o2.pl>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Adrian Bunk <bunk@kernel.org>, Andi Kleen <ak@suse.de>,
	Randy Dunlap <randy.dunlap@oracle.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org
Subject: Re: RFC: drop support for gcc < 4.0
Date: Wed, 22 Aug 2007 09:36:22 +0200	[thread overview]
Message-ID: <20070822073622.GB1684@ff.dom.local> (raw)
In-Reply-To: <alpine.LFD.0.999.0708211332330.30176@woody.linux-foundation.org>

On Tue, Aug 21, 2007 at 01:32:50PM -0700, Linus Torvalds wrote:
> 
> 
> On Tue, 21 Aug 2007, Adrian Bunk wrote:
> > 
> > How many people e.g. test -rc kernels compiled with gcc 3.2?
> 
> How could anybody know?

It shouldn't be so hard:

a) statistically: by doing some random math with:

int number_of_seemingly_gcc3.2_reports_eg_per_rc;
int number_of_all_such_reports_eg_per_rc;
int estimated_number_of_all_users_or_developers;
(or maybe some more...)

b) precisely (or even more): by adding proper and often updated
announcements, e.g:

"drivers/usb/host/ohci-pci.c:202: warning: unused variable `pdev'
(BTW, Angelina and Brad will be very suprised this warning is
yet possible!!!)"

Regards,
Jarek P.

  reply	other threads:[~2007-08-22  7:35 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20070821132038.GA22254@ff.dom.local>
     [not found] ` <20070821093103.3c097d4a.randy.dunlap@oracle.com>
2007-08-21 17:35   ` RFC: drop support for gcc < 4.0 Adrian Bunk
2007-08-21 17:54     ` Russell King
2007-08-21 18:14       ` Kyle McMartin
2007-08-21 18:29       ` Adrian Bunk
2007-08-22  5:48         ` Robert P. J. Day
2007-08-21 18:25     ` Chris Wedgwood
2007-08-21 20:41       ` Glauber de Oliveira Costa
2007-08-21 20:56         ` Segher Boessenkool
2007-08-21 21:01           ` Glauber de Oliveira Costa
2007-08-22  6:59         ` Thomas Bogendoerfer
2007-08-22 18:15         ` Ralf Baechle
2007-08-21 19:19     ` Andi Kleen
2007-08-21 19:54       ` Adrian Bunk
2007-08-21 20:07         ` [RFC][PATCH] introduce TASK_SIZE_OF() for all arches Matthew Wilcox
2007-08-21 20:08         ` RFC: drop support for gcc < 4.0 Linus Torvalds
2007-08-21 20:21           ` Adrian Bunk
2007-08-21 20:32             ` Linus Torvalds
2007-08-22  7:36               ` Jarek Poplawski [this message]
2007-08-21 20:49             ` Segher Boessenkool
2007-08-21 21:21               ` Adrian Bunk
2007-08-21 21:49                 ` James Bottomley
2007-08-21 22:09                   ` Adrian Bunk
2007-08-22  0:08                 ` Segher Boessenkool
2007-08-22  6:07                   ` Jarek Poplawski
2007-08-21 21:41     ` Oliver Pinter
2007-08-22  7:57       ` Jan Engelhardt
2007-08-22  8:08         ` Jarek Poplawski
2007-08-22  8:10           ` Jan Engelhardt
2007-08-22  8:42             ` Michal Piotrowski
2007-08-22  8:56             ` Jarek Poplawski
2007-08-22  8:48         ` Martin Michlmayr

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=20070822073622.GB1684@ff.dom.local \
    --to=jarkao2@o2.pl \
    --cc=ak@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=bunk@kernel.org \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=randy.dunlap@oracle.com \
    --cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).