From: Greg KH <greg@kroah.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Masahiro Yamada <yamada.masahiro@socionext.com>,
"H. Nikolaus Schaller" <hns@goldelico.com>,
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>,
linux-kbuild <linux-kbuild@vger.kernel.org>
Subject: Re: [PATCH v2] modules_install: make missing $DEPMOD a warning instead of error
Date: Thu, 23 Aug 2018 19:59:49 +0200 [thread overview]
Message-ID: <20180823175949.GB14106@kroah.com> (raw)
In-Reply-To: <61369202-8425-4cb7-aa9d-b83f15c528e0@infradead.org>
On Thu, Aug 23, 2018 at 10:52:39AM -0700, Randy Dunlap wrote:
> From: Randy Dunlap <rdunlap@infradead.org>
>
> When $DEPMOD is not found, only print a warning instead of exiting
> with an error message and error status.
>
> Warning: 'make modules_install' requires /sbin/depmod. Please install it.
> This is probably in the kmod package.
>
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
> ---
> v2: add missing "exit 0" and update the commit message (no Error).
You need a cc: stable in here too :(
prev parent reply other threads:[~2018-08-23 21:30 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
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 [this message]
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=20180823175949.GB14106@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-kbuild@vger.kernel.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 \
--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