From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Luis Chamberlain <mcgrof@kernel.org>
Cc: Randy Dunlap <rdunlap@infradead.org>,
kernel test robot <lkp@intel.com>,
kbuild-all@lists.01.org, linux-kernel@vger.kernel.org
Subject: Re: kernel/module_decompress.c:264:36: error: 'module_kset' undeclared; did you mean 'module_use'?
Date: Tue, 15 Feb 2022 13:06:19 -0800 [thread overview]
Message-ID: <YgwVy598bcqbaHtb@google.com> (raw)
In-Reply-To: <YgtX9OFbeNZdCZTp@bombadil.infradead.org>
On Mon, Feb 14, 2022 at 11:36:20PM -0800, Luis Chamberlain wrote:
> On Sun, Feb 13, 2022 at 06:55:45PM -0800, Dmitry Torokhov wrote:
> > On Sun, Feb 13, 2022 at 04:34:49PM -0800, Randy Dunlap wrote:
> > >
> > >
> > > On 2/13/22 08:57, kernel test robot wrote:
> > > > tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> > > > head: b81b1829e7e39f6cebdf6e4d5484eacbceda8554
> > > > commit: b1ae6dc41eaaa98bb75671e0f3665bfda248c3e7 module: add in-kernel support for decompressing
> > > > date: 5 weeks ago
> > > > config: sparc-randconfig-r005-20220213 (https://download.01.org/0day-ci/archive/20220214/202202140027.K0xZn3T2-lkp@intel.com/config)
> > > > compiler: sparc-linux-gcc (GCC) 11.2.0
> > > > reproduce (this is a W=1 build):
> > > > wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
> > > > chmod +x ~/bin/make.cross
> > > > # https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=b1ae6dc41eaaa98bb75671e0f3665bfda248c3e7
> > > > git remote add linus https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
> > > > git fetch --no-tags linus master
> > > > git checkout b1ae6dc41eaaa98bb75671e0f3665bfda248c3e7
> > > > # save the config file to linux build tree
> > > > mkdir build_dir
> > > > COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross O=build_dir ARCH=sparc SHELL=/bin/bash
> > >
> > > FTR/FYI:
> > > # CONFIG_SYSFS is not set
> >
> > Ugh, why is this even a thing?
>
> If the kconfig supports it we need to support it. If you think
> we need to remove the option to be built-in we can take that
> up separately. In the meantime it would be wonderful if you
> can address this issue for Linus' tree.
Yes, of course, I was just wondering why we still have option to disable
sysfs. I guess some very purpose-built embedded systems might still
function without it...
--
Dmitry
prev parent reply other threads:[~2022-02-15 21:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-13 16:57 kernel test robot
2022-02-14 0:34 ` Randy Dunlap
2022-02-14 2:55 ` Dmitry Torokhov
2022-02-15 7:36 ` Luis Chamberlain
2022-02-15 21:06 ` Dmitry Torokhov [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=YgwVy598bcqbaHtb@google.com \
--to=dmitry.torokhov@gmail.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=mcgrof@kernel.org \
--cc=rdunlap@infradead.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
all inboxes | Powered by JetHome®