From: Randy Dunlap <rdunlap@infradead.org>
To: Rohit Sarkar <rohitsarkar5398@gmail.com>
Cc: linux-newbie@vger.kernel.org, kernel-janitors@vger.kernel.org,
linux-iio@vger.kernel.org
Subject: Re: Problems during compiling in kernel modules
Date: Sat, 14 Sep 2019 08:23:07 -0700 [thread overview]
Message-ID: <cffb789d-1464-c194-bfc4-bc05a5ac9db7@infradead.org> (raw)
In-Reply-To: <20190914063136.GA23166@SARKAR>
On 9/13/19 11:31 PM, Rohit Sarkar wrote:
> On Fri, Sep 13, 2019 at 03:36:03PM -0700, Randy Dunlap wrote:
>> Hi,
>> It works for me. Do you have a kernel .config file?
>> Does it set/enable CONFIG_IIO and some/any/all drivers in drivers/iio/accel/ ?
>>
>> If you don't have a kernel .config file, I don't expect it to work.
>> --
>> ~Randy
>
> Hey Randy,
> I do have a .config file but no it does not set "CONFIG_IIO".
> The weird thing is when I built the kernel initially the object files
> for drivers/iio/accel/ were generated.
> That's strange right?
Sounds like you now have a different .config file and that the earlier
.config file did enable CONFIG_IIO.
--
~Randy
next prev parent reply other threads:[~2019-09-14 15:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190913173821.GA5986@SARKAR>
2019-09-13 18:01 ` Problems during compiling in kernel modules Rohit Sarkar
2019-09-13 22:36 ` Randy Dunlap
2019-09-14 6:31 ` Rohit Sarkar
2019-09-14 15:23 ` Randy Dunlap [this message]
2019-09-14 4:57 ` Jay Aurabind
2019-09-14 5:57 ` Julia Lawall
2019-09-14 14:25 ` Rohit Sarkar
2019-09-14 14:35 ` Julia Lawall
2019-09-14 14:45 ` Rohit Sarkar
2019-09-14 15:01 ` Randy Dunlap
2019-09-14 14:37 ` Rohit Sarkar
2019-09-14 14:44 ` Julia Lawall
2019-09-14 9:55 ` Austin Kim
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=cffb789d-1464-c194-bfc4-bc05a5ac9db7@infradead.org \
--to=rdunlap@infradead.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-newbie@vger.kernel.org \
--cc=rohitsarkar5398@gmail.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).