From: Michal Nazarewicz <mina86@tlen.pl>
To: Mulyadi Santosa <mulyadi.santosa@gmail.com>
Cc: Balachandar <bala1486@gmail.com>,
kernelnewbies@nl.linux.org, linux-c-programming@vger.kernel.org
Subject: Re: Error in compiling a module
Date: Thu, 29 Jul 2010 18:21:45 +0200 [thread overview]
Message-ID: <87lj8u9s2u.fsf@erwin.mina86.com> (raw)
In-Reply-To: <AANLkTimeJrRs4Bd1aw--FKPYyqcuu8_O-Xi5G0FOh0yd@mail.gmail.com> (Mulyadi Santosa's message of "Thu, 29 Jul 2010 11:51:04 +0700")
[-- Attachment #1: Type: text/plain, Size: 824 bytes --]
Mulyadi Santosa <mulyadi.santosa@gmail.com> writes:
> Hi...
>
> On Thu, Jul 29, 2010 at 00:28, Balachandar <bala1486@gmail.com> wrote:
>> Thank you for your help. I figured out the mistake. I missed a
>> semicolon in one of the header file that was included in the file that
>> showed the error.
>
> I think it would be great if you and some guys here write about
> "mistakes I ever did when I write kernel codes" in kernelnewbies
> wiki....so that others might learn about it.
Personally, I see it as a suggestion for a wikibooks or similar.
--
Best regards, _ _
.o. | Liege of Serenly Enlightened Majesty of o' \,=./ `o
..o | Computer Science, Michal "mina86" Nazarewicz (o o)
ooo +--<mina86-tlen.pl>--<jid:mina86-jabber.org>--ooO--(_)--Ooo--
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2010-07-29 16:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-27 21:17 Error in compiling a module Balachandar
2010-07-27 22:30 ` Michal Nazarewicz
2010-07-28 4:59 ` Mulyadi Santosa
2010-07-28 17:28 ` Balachandar
2010-07-29 4:51 ` Mulyadi Santosa
2010-07-29 13:56 ` Victor Rodriguez
2010-07-29 13:56 ` Victor Rodriguez
2010-07-29 16:21 ` Michal Nazarewicz [this message]
2010-07-29 17:52 ` Mulyadi Santosa
2010-07-29 18:10 ` Jim Cromie
2010-07-29 20:23 ` Mulyadi Santosa
2010-07-29 20:35 ` Greg Freemyer
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=87lj8u9s2u.fsf@erwin.mina86.com \
--to=mina86@tlen.pl \
--cc=bala1486@gmail.com \
--cc=kernelnewbies@nl.linux.org \
--cc=linux-c-programming@vger.kernel.org \
--cc=mulyadi.santosa@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.