From: Greg Kroah-Hartman <gregkh@linuxfoundation•org>
To: Eli Billauer <eli.billauer@gmail•com>
Cc: Randy Dunlap <rdunlap@infradead•org>,
akpm@linux-foundation•org, broonie@kernel•org,
linux-fsdevel@vger•kernel.org, linux-kernel@vger•kernel.org,
linux-mm@kvack•org, linux-next@vger•kernel.org, mhocko@suse•cz,
mm-commits@vger•kernel.org, sfr@canb•auug.org.au
Subject: Re: mmotm 2021-06-01-19-57 uploaded (xillybus)
Date: Thu, 3 Jun 2021 14:10:53 +0200 [thread overview]
Message-ID: <YLjGzWmli7ZpP4O3@kroah.com> (raw)
In-Reply-To: <60B8B189.6060404@gmail.com>
On Thu, Jun 03, 2021 at 01:40:09PM +0300, Eli Billauer wrote:
> On 02/06/21 08:00, Greg Kroah-Hartman wrote:
> > > (on i386)
> > > > > CONFIG_XILLYBUS_CLASS=y
> > > > CONFIG_XILLYBUS=m
> > > > CONFIG_XILLYUSB=y
> > > > > ERROR: modpost: "xillybus_cleanup_chrdev"
> > > [drivers/char/xillybus/xillybus_core.ko] undefined!
> > > > ERROR: modpost: "xillybus_init_chrdev" [drivers/char/xillybus/xillybus_core.ko] undefined!
> > > > ERROR: modpost: "xillybus_find_inode" [drivers/char/xillybus/xillybus_core.ko] undefined!
> > > > > > Full randconfig file is attached.
> > Sorry about that, I have a fix in my inbox for this that I will push out
> > later today...
> For the record, this is the said pending patch:
>
> https://lkml.org/lkml/2021/5/28/245
>
> I've tested this issue, and can confirm the compilation problem and that the
> patch fixes it.
Now queued up, thanks.
greg k-h
prev parent reply other threads:[~2021-06-03 12:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-02 2:58 mmotm 2021-06-01-19-57 uploaded akpm
2021-06-02 4:03 ` mmotm 2021-06-01-19-57 uploaded (xillybus) Randy Dunlap
2021-06-02 5:00 ` Greg Kroah-Hartman
2021-06-03 10:40 ` Eli Billauer
2021-06-03 12:10 ` Greg Kroah-Hartman [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=YLjGzWmli7ZpP4O3@kroah.com \
--to=gregkh@linuxfoundation$(echo .)org \
--cc=akpm@linux-foundation$(echo .)org \
--cc=broonie@kernel$(echo .)org \
--cc=eli.billauer@gmail$(echo .)com \
--cc=linux-fsdevel@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-mm@kvack$(echo .)org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=mhocko@suse$(echo .)cz \
--cc=mm-commits@vger$(echo .)kernel.org \
--cc=rdunlap@infradead$(echo .)org \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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