linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@digeo.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: alan@lxorguk.ukuu.org.uk, torvalds@transmeta.com, perex@suse.cz,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Isapnp warning
Date: Sat, 21 Jun 2003 12:51:11 -0700	[thread overview]
Message-ID: <20030621125111.0bb3dc1c.akpm@digeo.com> (raw)
In-Reply-To: <Pine.GSO.4.21.0306211658470.869-100000@vervain.sonytel.be>

Geert Uytterhoeven <geert@linux-m68k.org> wrote:
>
> > >  int pnp_add_irq_resource(struct pnp_dev *dev, int depnum, struct pnp_irq *data)
>  > >  {
>  > > +#ifdef CONFIG_PCI
>  > >  	int i;
>  > > +#endif
>  > 
>  > This is far uglier than te warning
> 
>  It depends on your goals. These warnings distract us from the real harmful
>  warnings. Will we ever have a kernel that compiles with -Werror?

It would be nice.  But as soon as we do that, some gcc guy will have a
brainfart and we'll get a whole new batch of warnings which we cannot turn
off.  Again.  I've been involved in projects where it was unacceptable to
upgrade the gcc version for this sole reason.


Meanwhile, let's do this:

diff -puN drivers/pnp/resource.c~misc6 drivers/pnp/resource.c
--- 25/drivers/pnp/resource.c~misc6	2003-06-21 12:47:23.000000000 -0700
+++ 25-akpm/drivers/pnp/resource.c	2003-06-21 12:47:44.000000000 -0700
@@ -97,7 +97,6 @@ int pnp_get_max_depnum(struct pnp_dev *d
 
 int pnp_add_irq_resource(struct pnp_dev *dev, int depnum, struct pnp_irq *data)
 {
-	int i;
 	struct pnp_resources *res;
 	struct pnp_irq *ptr;
 	res = pnp_find_resources(dev,depnum);
@@ -113,9 +112,13 @@ int pnp_add_irq_resource(struct pnp_dev 
 	else
 		res->irq = data;
 #ifdef CONFIG_PCI
-	for (i=0; i<16; i++)
-		if (data->map & (1<<i))
-			pcibios_penalize_isa_irq(i);
+	{
+		int i;
+
+		for (i=0; i<16; i++)
+			if (data->map & (1<<i))
+				pcibios_penalize_isa_irq(i);
+	}
 #endif
 	return 0;
 }

_


  parent reply	other threads:[~2003-06-21 19:36 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-15 18:36 [PATCH] Isapnp warning Geert Uytterhoeven
2003-06-21 12:31 ` Alan Cox
2003-06-21 14:59   ` Geert Uytterhoeven
2003-06-21 15:04     ` Sean Neakums
2003-06-21 19:51     ` Andrew Morton [this message]
2003-06-21 23:53       ` Linus Torvalds
2003-06-22  0:11         ` Arnaldo Carvalho de Melo
2003-06-22  1:41           ` Chris Wedgwood
2003-06-22  1:43             ` Arnaldo Carvalho de Melo
2003-06-22  2:17               ` Andrew Morton
2003-06-22  2:27                 ` Chris Wedgwood
2003-06-22  2:59                   ` Andrew Morton
2003-06-22  5:50                     ` Herbert Xu
2003-06-22  3:43                 ` Martin J. Bligh
2003-06-22  4:24                 ` Paul Mackerras
2003-06-22  8:32                   ` Geert Uytterhoeven
2003-06-22 13:34                     ` Daniel Phillips
2003-06-22  5:39                 ` gcc 3.3: largest *and* smallest kernels (was Re: [PATCH] Isapnp warning) Barry K. Nathan
2003-06-22 11:31                   ` Alan Cox
2003-06-22 13:22                 ` GCC speed (was " Daniel Phillips
2003-06-22 17:32                   ` Andrew Morton
2003-06-22 17:56                     ` Linus Torvalds
2003-06-22 18:58                     ` Henning P. Schmiedehausen
2003-06-22 19:12                       ` Sam Ravnborg
2003-06-22 19:13                       ` Andrew Morton
2003-06-22 19:32                         ` Henning Schmiedehausen
2003-06-22 19:51                       ` Adrian Bunk
2003-06-22 19:12                     ` Daniel Phillips
2003-06-23  1:05                     ` Larry McVoy
2002-01-04 11:32                       ` Pavel Machek
2003-07-17 10:18                         ` Christoph Hellwig
2003-07-17 10:23                           ` Jakub Jelinek
2003-07-17 10:27                             ` Christoph Hellwig
2003-06-22  8:49               ` [PATCH] Isapnp warning Russell King
2003-06-22  8:39             ` Jörn Engel
2003-06-22 14:07   ` Daniel Phillips
2003-06-22 15:00     ` Jan-Benedict Glaw
  -- strict thread matches above, loose matches on Subject: below --
2003-08-29 14:49 Geert Uytterhoeven
2003-06-15 19:10 Geert Uytterhoeven
2003-06-09 10:37 Geert Uytterhoeven

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=20030621125111.0bb3dc1c.akpm@digeo.com \
    --to=akpm@digeo.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=geert@linux-m68k.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=perex@suse.cz \
    --cc=torvalds@transmeta.com \
    /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).