From: Greg KH <greg@kroah.com>
To: Omar Mustafa <omarmustafa1991@yahoo.com>
Cc: kernelnewbies@kernelnewbies.org
Subject: Re: Vmalloc.h implicit functions
Date: Tue, 7 Sep 2021 14:53:40 +0200 [thread overview]
Message-ID: <YTdg1Apkl/jAiNzJ@kroah.com> (raw)
In-Reply-To: <9C5D07C3-48AA-4E1A-9998-28E94DFCCB08@yahoo.com>
On Tue, Sep 07, 2021 at 02:41:57PM +0200, Omar Mustafa wrote:
> Hi all,
>
> I’m trying to install some modules but yet I fail with those errors:
>
> error: too many arguments to function ‘__vmalloc’ 157 |
> __vmalloc(load_driver->sys_files[i].size,
>
> ./include/linux/vmalloc.h:132:14: note: declared here
> 132 | extern void *__vmalloc(unsigned long size, gfp_t gfp_mask);
What out-of-tree drivers are you trying to build? Please fix them up to
handle the new api changes.
> Hence, make fails every time.
Then fix the drivers, they are under your control :)
> I was hoping whether there is any solution to this problems since
> Bluetooth driver build for example fails and I need it working for
> some IoT projects I am currently working on.
What exact driver is failing?
thanks,
greg k-h
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next prev parent reply other threads:[~2021-09-07 12:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <9C5D07C3-48AA-4E1A-9998-28E94DFCCB08.ref@yahoo.com>
2021-09-07 12:41 ` Vmalloc.h implicit functions Omar Mustafa
2021-09-07 12:53 ` Greg KH [this message]
2021-09-07 16:06 ` Omar Mustafa
2021-09-07 16:17 ` Greg KH
2021-09-07 22:34 ` Valdis Klētnieks
[not found] ` <B4A71321-4D9C-4FB1-BD7D-AB3BF2FE9D7B@yahoo.com>
2021-09-08 5:54 ` Valdis Klētnieks
[not found] ` <6698A2F7-4242-4B6B-9C59-D651FA7337E7@yahoo.com>
2021-09-09 1:39 ` Valdis Klētnieks
[not found] ` <B91EDE80-8B43-415D-9969-AFF2EB3FA414@yahoo.com>
2021-09-15 14:42 ` 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=YTdg1Apkl/jAiNzJ@kroah.com \
--to=greg@kroah.com \
--cc=kernelnewbies@kernelnewbies.org \
--cc=omarmustafa1991@yahoo.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).