From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.kernel.org ([198.145.29.99]:44118 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726186AbgAHPsh (ORCPT ); Wed, 8 Jan 2020 10:48:37 -0500 Date: Wed, 8 Jan 2020 16:48:35 +0100 From: Greg Kroah-Hartman Subject: Re: [PATCH] kbuild: allow modules to link *.a archives Message-ID: <20200108154835.GA2449518@kroah.com> References: <20200106032324.3147-1-masahiroy@kernel.org> <20200108154406.GA21695@infradead.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20200108154406.GA21695@infradead.org> Sender: linux-kbuild-owner@vger.kernel.org List-ID: To: Christoph Hellwig Cc: Masahiro Yamada , linux-kbuild@vger.kernel.org, Fumiya Shigemitsu , Yongxin Liu , Michal Marek , linux-kernel@vger.kernel.org On Wed, Jan 08, 2020 at 07:44:06AM -0800, Christoph Hellwig wrote: > On Mon, Jan 06, 2020 at 12:23:24PM +0900, Masahiro Yamada wrote: > > Since commit 69ea912fda74 ("kbuild: remove unneeded link_multi_deps"), > > modules cannot link *.a archives. > > > > I do not see such a usecase in the upstream code, but multiple people > > reported this issue, so it seems to be a desired feature for external > > modules. > > Kernel policy is to not keep around infrastructure not used upstream. > And linking archives in the kernel doesn't really make any sense, so > this shouldn't go in in any form. Yeah, I agree, it's just going to bit-rot and people really shouldn't be doing stuff like this in their kernel modules. If they want to, they need to figure out how to do it themselves :) greg k-h