From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S264386AbUHWNxg (ORCPT ); Mon, 23 Aug 2004 09:53:36 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S264396AbUHWNxf (ORCPT ); Mon, 23 Aug 2004 09:53:35 -0400 Received: from parcelfarce.linux.theplanet.co.uk ([195.92.249.252]:15807 "EHLO www.linux.org.uk") by vger.kernel.org with ESMTP id S264386AbUHWNxc (ORCPT ); Mon, 23 Aug 2004 09:53:32 -0400 Date: Mon, 23 Aug 2004 09:34:30 -0300 From: Marcelo Tosatti To: "O.Sezer" Cc: linux-kernel@vger.kernel.org Subject: Re: [PATCH 2.4] gcc-3.4 more fixes Message-ID: <20040823123430.GD4569@logos.cnet> References: <4129F41A.3070805@ttnet.net.tr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4129F41A.3070805@ttnet.net.tr> User-Agent: Mutt/1.5.5.1i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Aug 23, 2004 at 04:41:46PM +0300, O.Sezer wrote: > >>Ozkan, > >> > >>This are just warning fixes right? > >> > >>I dont like this patches, that is, I'm not confident about them. > >> > >> Let the warnings be. > > > > For gcc-3.4 they're warnings. For gcc-3.5 they'll cause compiler > > failures (that's what mikpe says on cset-1.1490, too) > > As a side note, almost all of them are in 2.6 anyway (can't > honestly remember which aren't) Have you nocited the deadly mistake you made I showed with the grep?