linux-pm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Shaun Tancheff <shaun@tancheff.com>
To: Masahiro Yamada <yamada.masahiro@socionext.com>
Cc: Shaun Tancheff <stancheff@cray.com>,
	linux-kbuild@vger.kernel.org,
	Joe Lawrence <joe.lawrence@redhat.com>,
	"'James E . J . Bottomley'" <jejb@linux.ibm.com>,
	Jonathan Corbet <corbet@lwn.net>,
	"'Martin K . Petersen'" <martin.petersen@oracle.com>,
	Michal Marek <michal.lkml@markovi.net>,
	Shuah Khan <shuah@kernel.org>, Thomas Renninger <trenn@suse.com>,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-pm@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: [PATCH 0/1] kbuild: Support building a tree of modules with -M=<root>
Date: Thu,  8 Aug 2019 19:21:03 -0500	[thread overview]
Message-ID: <20190809002104.18599-1-stancheff@cray.com> (raw)

Currently when building lustre against 5.3 kernel modules fail to
generate <module>.ko files.

Lustre builds a tree of modules however the numerous modules.order files
are created but only the modules.order file at the root appears to be 
read.

This changes the the scheme for KBUILD_EXTMOD to write to and read from
a single modules.order file at the root.

Shaun Tancheff (1):
  kbuild: recursive build of external kernel modules

 Makefile               | 1 +
 scripts/Makefile.build | 8 +++++++-
 2 files changed, 8 insertions(+), 1 deletion(-)

-- 
2.20.1


             reply	other threads:[~2019-08-09  0:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-09  0:21 Shaun Tancheff [this message]
2019-08-09  0:21 ` [PATCH 1/1] kbuild: recursive build of external kernel modules Shaun Tancheff
2019-08-12 15:23   ` Masahiro Yamada
2019-08-12 17:34     ` Shaun Tancheff
2019-08-13  1:06       ` Masahiro Yamada
2019-08-13 22:10         ` Shaun Tancheff

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=20190809002104.18599-1-stancheff@cray.com \
    --to=shaun@tancheff.com \
    --cc=corbet@lwn.net \
    --cc=jejb@linux.ibm.com \
    --cc=joe.lawrence@redhat.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=michal.lkml@markovi.net \
    --cc=shuah@kernel.org \
    --cc=stancheff@cray.com \
    --cc=trenn@suse.com \
    --cc=yamada.masahiro@socionext.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).