Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756279Ab1DZON7 (ORCPT ); Tue, 26 Apr 2011 10:13:59 -0400 Received: from nd215.dnsexit.com ([64.182.102.215]:60775 "EHLO box7.911domain.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1754811Ab1DZON6 (ORCPT ); Tue, 26 Apr 2011 10:13:58 -0400 X-Complaints-To: abuse@dnsExit.com X-SPAM: Please report Spam to abuse@dnsExit.com By service at http://www.dnsExit.com/Direct.sv?cmd=mailRelay Accounts will be suspended immediately if convicted Spam Message-ID: <4DB6D2F7.4000908@verizon.net> Date: Tue, 26 Apr 2011 10:13:11 -0400 From: Peter Foley Reply-To: User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9 MIME-Version: 1.0 To: Arnaud Lacombe CC: , , Subject: Re: [PATCH] kbuild: scripts/kconfig/Makefile cleanup and fixes References: <4DB60DE1.8060402@verizon.net> In-Reply-To: Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 993 Lines: 29 On 4/26/2011 2:38 AM, Arnaud Lacombe wrote: > Hi, > > On Mon, Apr 25, 2011 at 8:12 PM, Peter Foley wrote: >> This patch: >> Changes the update-po-config target to work when make is run from KBUILD_OUTDIR. >> Adds a check to only build kxgettext when needed. >> Changes the qconf and gconf targets to change hostprogs-y when they are being built >> like nconfig and menuconfig instead of defining *-objs. >> Cleans up the clean-files definitions. >> > Would it be possible to split that one into several patches, one for > each change ? Associating the diff and to log is pretty much > impossible. From the commit message, that should be 4 patches. > > Thanks, > - Arnaud > Ok, I'll do that. Thanks, Peter Foley -- 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/