From: Greg KH <greg@kroah.com>
To: "H. Nikolaus Schaller" <hns@goldelico.com>
Cc: Randy Dunlap <rdunlap@infradead.org>,
Lucas De Marchi <lucas.demarchi@profusion.mobi>,
Lucas De Marchi <lucas.de.marchi@gmail.com>,
Michal Marek <michal.lkml@markovi.net>,
Jessica Yu <jeyu@kernel.org>,
Chih-Wei Huang <cwhuang@linux.org.tw>,
stable <stable@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Discussions about the Letux Kernel
<letux-kernel@openphoenux.org>
Subject: Re: please revert commit ce8556cca6 "kbuild: verify that $DEPMOD is installed" introduced in v4.18.4.
Date: Wed, 22 Aug 2018 21:10:48 +0200 [thread overview]
Message-ID: <20180822191048.GA6916@kroah.com> (raw)
In-Reply-To: <490A46D5-834E-46A9-9106-A31F94344F99@goldelico.com>
On Wed, Aug 22, 2018 at 08:53:46PM +0200, H. Nikolaus Schaller wrote:
> This patch requires that /sbin/depmod is installed and installable on
> the build host.
>
> But not all build hosts for cross compiling Linux are Linux systems
> and are able to provide a working port of depmod, especially at the
> file patch /sbin/depmod.
>
> I use, for example, a Darwin system to cross compile Linux and I run
> depmod -a on the embedded system once, after installing a new Linux
> kernel there.
>
> I have no problem with seeing a warning, but aborting the build process
> is IMHO a bad idea since the previous behaviour didn't harm many people
> as far as I see. Probably 99% of people compiling Linux kernels do that
> on Linux and 99% of those have depmod installed for optimal operation of
> their build host. So IMHO printing the warning is good enough.
It needs to be reverted in Linus's tree first before I can revert it in
the stable tree(s).
thanks,
greg k-h
next prev parent reply other threads:[~2018-08-22 19:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-22 18:53 please revert commit ce8556cca6 "kbuild: verify that $DEPMOD is installed" introduced in v4.18.4 H. Nikolaus Schaller
2018-08-22 19:10 ` Greg KH [this message]
2018-08-22 23:33 ` Randy Dunlap
2018-08-23 0:39 ` Dmitry Torokhov
2018-08-23 1:07 ` Randy Dunlap
2018-08-23 7:16 ` H. Nikolaus Schaller
2018-08-23 7:20 ` Masahiro Yamada
2018-08-23 8:38 ` Masahiro Yamada
2018-08-23 15:55 ` Alexander Kapshuk
2018-08-23 17:52 ` [PATCH v2] modules_install: make missing $DEPMOD a warning instead of error Randy Dunlap
2018-08-23 17:59 ` Greg KH
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=20180822191048.GA6916@kroah.com \
--to=greg@kroah.com \
--cc=cwhuang@linux.org.tw \
--cc=hns@goldelico.com \
--cc=jeyu@kernel.org \
--cc=letux-kernel@openphoenux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lucas.de.marchi@gmail.com \
--cc=lucas.demarchi@profusion.mobi \
--cc=michal.lkml@markovi.net \
--cc=rdunlap@infradead.org \
--cc=stable@vger.kernel.org \
/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