Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755181AbYFHRIG (ORCPT ); Sun, 8 Jun 2008 13:08:06 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752797AbYFHRHv (ORCPT ); Sun, 8 Jun 2008 13:07:51 -0400 Received: from gate.crashing.org ([63.228.1.57]:41670 "EHLO gate.crashing.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752227AbYFHRHc (ORCPT ); Sun, 8 Jun 2008 13:07:32 -0400 In-Reply-To: <1212931024.32207.546.camel@pmac.infradead.org> References: <20080608094730.GA30098@uranus.ravnborg.org> <19f34abd0806080312j2b09179cpa384a0460af5874e@mail.gmail.com> <20080608104122.GA10545@uranus.ravnborg.org> <1212922141.32207.495.camel@pmac.infradead.org> <20080608111707.GB10545@uranus.ravnborg.org> <1212931024.32207.546.camel@pmac.infradead.org> Mime-Version: 1.0 (Apple Message framework v623) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <2ccd2be2a739abf56d86266d5041bf07@kernel.crashing.org> Content-Transfer-Encoding: 7bit Cc: Vegard Nossum , geert@linux-m68k.org, LKML , Linus Torvalds , linux-kbuild , zippel@linux-m68k.org, Sam Ravnborg , Jan Engelhardt From: Segher Boessenkool Subject: Re: [PATCH] Speed up "make headers_*" Date: Sun, 8 Jun 2008 19:06:46 +0200 To: David Woodhouse X-Mailer: Apple Mail (2.623) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 655 Lines: 18 > Assuming we _don't_ want the ac_ahz member to be included on m68k, this > should fix it (is __mc68000__ the right thing to use?)... I think __m68k__ is preferred, it's harder to confuse for one of the tuning symbols (that is, __mc68040__ and friends). It should function identically though, both __m68k__ and __mc68000__ (and __mc68000 and mc68000) are defined under exactly the same conditions. Segher -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/