All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Masahiro Yamada <masahiroy@kernel.org>
Cc: linux-kbuild@vger.kernel.org,
	Fumiya Shigemitsu <shfy1014@gmail.com>,
	Yongxin Liu <yongxin.liu@windriver.com>,
	Michal Marek <michal.lkml@markovi.net>,
	linux-kernel@vger.kernel.org,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [PATCH] kbuild: allow modules to link *.a archives
Date: Wed, 8 Jan 2020 07:44:06 -0800	[thread overview]
Message-ID: <20200108154406.GA21695@infradead.org> (raw)
In-Reply-To: <20200106032324.3147-1-masahiroy@kernel.org>

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.

  parent reply	other threads:[~2020-01-08 15:44 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-06  3:23 [PATCH] kbuild: allow modules to link *.a archives Masahiro Yamada
2020-01-06  6:12 ` kbuild test robot
2020-01-06  6:12   ` kbuild test robot
2020-01-06  6:12   ` kbuild test robot
2020-01-06  6:47 ` kbuild test robot
2020-01-06  6:47   ` kbuild test robot
2020-01-06  6:47   ` kbuild test robot
2020-01-08 15:44 ` Christoph Hellwig [this message]
2020-01-08 15:48   ` Greg Kroah-Hartman
2020-01-11  7:22     ` Masahiro Yamada

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200108154406.GA21695@infradead.org \
    --to=hch@infradead.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=masahiroy@kernel.org \
    --cc=michal.lkml@markovi.net \
    --cc=shfy1014@gmail.com \
    --cc=yongxin.liu@windriver.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.