Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752703AbaG0SkV (ORCPT ); Sun, 27 Jul 2014 14:40:21 -0400 Received: from asavdk3.altibox.net ([109.247.116.14]:33081 "EHLO asavdk3.altibox.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752571AbaG0SkS (ORCPT ); Sun, 27 Jul 2014 14:40:18 -0400 Date: Sun, 27 Jul 2014 20:40:10 +0200 From: Sam Ravnborg To: Ard Biesheuvel Cc: Andreas Schwab , "linux-arm-kernel@lists.infradead.org" , "linux-kernel@vger.kernel.org" Subject: Re: [PATCH] arm64/crypto: fix makefile rule for aes-glue-%.o Message-ID: <20140727184010.GA26029@ravnborg.org> References: <20140724161225.GA11204@ravnborg.org> <20140724204526.GA11754@ravnborg.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > > > Btw. the current solution is already faulty - even with the fix. > > There are no support for make C=2 arch/.../crypto/ > > > > So can you elaborate on how it is faulty? When you run "make C=2 arch/.../crypto/" then sparse shall be run for all .c files also if they are already built. But due to the re-implementation of some parts of the kbuild logic in the makefile this does not happen with the -glue file. A minor detail - but this may not be the only wreckage we see over time. Sam -- 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/