From: Kumar Gaurav <kumargauravgupta3@gmail.com>
To: kernel-janitors@vger.kernel.org
Subject: Re: Help required for Compiling a staging driver
Date: Mon, 14 Apr 2014 18:59:24 +0000 [thread overview]
Message-ID: <534C2D3C.6030100@gmail.com> (raw)
In-Reply-To: <20140414184618.GA13336@kroah.com>
On Tuesday 15 April 2014 12:16 AM, Greg KH wrote:
> On Tue, Apr 15, 2014 at 12:08:18AM +0530, Kumar Gaurav wrote:
>> Hi All,
>>
>> I'm trying to upgrade a driver using semaphore to use mutex. I have
>> applied the required changes. Now i want to compile it to ensure that i
>> didn't broke the kernel.
>>
>> Driver Path:drivers/staging/dgap/
>> I Marked this driver to load as loadable module
>>
>> kumar@anandlinux:/usr/linux-git$ grep CONFIG_DGAP .config
>> CONFIG_DGAP=m
>>
>> Now I'm trying to compile it using below command and getting result as given
>> kumar@anandlinux:/usr/linux-git$ sudo make M=drivers/staging/dgap/
>> Building modules, stage 2.
>> MODPOST 0 modules
> Never build kernel code as root. We used to have a bug in the build
> system that if you did this, it would delete your whole filesystem.
> Some of us argued that we should leave it there just to keep people from
> ever doing this again :)
>
>> So, No module is getting build and again i'm not getting any Error as
>> well. Please tell me where i'm doing wrong.
> Have you built this kernel source tree before? Do a full build first,
> before trying to just build one directory. That should resolve the
> issue.
What does it mean by full build? You mean compiling All modules? If yes
then is there anyway to mark all module at once or i need to mark
everything one by one (i use menuconfig)?
> And again, not as root please.
>
> greg k-h
prev parent reply other threads:[~2014-04-14 18:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-14 18:46 Help required for Compiling a staging driver Greg KH
2014-04-14 18:50 ` Kumar Gaurav
2014-04-14 18:55 ` Greg KH
2014-04-14 18:58 ` Andev
2014-04-14 18:59 ` Kumar Gaurav [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=534C2D3C.6030100@gmail.com \
--to=kumargauravgupta3@gmail.com \
--cc=kernel-janitors@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