public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Willy Tarreau <willy@w.ods.org>
To: "O.Sezer" <sezeroz@ttnet.net.tr>
Cc: bunk@fs.tum.de, marcelo.tosatti@cyclades.com,
	linux-kernel@vger.kernel.org
Subject: Re: [2.4 patch][5/6] asm-i386/smpboot.h: fix gcc 3.4 compilation
Date: Fri, 27 Aug 2004 00:18:56 +0200	[thread overview]
Message-ID: <20040826221856.GC564@alpha.home.local> (raw)
In-Reply-To: <412E4A4F.2040706@ttnet.net.tr>

On Thu, Aug 26, 2004 at 11:38:39PM +0300, O.Sezer wrote:
> Didn't look at the code much but how about removing the
> label as the -ac tree does?
> 

I remember I once had to add an empty default case in a switch/case in one of
my programs to stop gcc from complaining. I think it is the same here and the
'default' does not harm anyway.

And please remember, as a rule of thumb, if it does not change semantics nor
the code produced, please try to avoid moving parts of the stable kernel.
There are many people who have to apply other patches on top of a vanilla
kernel and who don't like it very much when they get rejects just because
of a recent code "beautification".

Regards,
Willy

> diff -urN 28pre2/include/asm-i386/smpboot.h 28pre2_acx/include/asm-i386/smpboot.h
> --- 28pre2/include/asm-i386/smpboot.h	2004-08-08 02:26:06.000000000 +0300
> +++ 28pre2_acx/include/asm-i386/smpboot.h	2004-08-26 12:09:44.000000000 +0300
> @@ -129,7 +129,6 @@
>  			/*round robin the interrupts*/
>  			cpu = (cpu+1)%smp_num_cpus;
>  			return cpu_to_physical_apicid(cpu);
> -		default:
>  	}
>  	return cpu_online_map;
>  }


  reply	other threads:[~2004-08-26 22:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-26 20:38 [2.4 patch][5/6] asm-i386/smpboot.h: fix gcc 3.4 compilation O.Sezer
2004-08-26 22:18 ` Willy Tarreau [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-08-26 19:51 [2.4 patch][0/6] fix compile errors with gcc 3.4 Adrian Bunk
2004-08-26 20:04 ` [2.4 patch][5/6] asm-i386/smpboot.h: fix gcc 3.4 compilation Adrian Bunk

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=20040826221856.GC564@alpha.home.local \
    --to=willy@w.ods.org \
    --cc=bunk@fs.tum.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo.tosatti@cyclades.com \
    --cc=sezeroz@ttnet.net.tr \
    /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