linux-c-programming.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mulyadi Santosa <mulyadi.santosa@gmail.com>
To: Jim Cromie <jim.cromie@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: Fri, 30 Jul 2010 03:23:31 +0700	[thread overview]
Message-ID: <AANLkTikcjw=xgCM73cenoxS9=oUM6jshtn=ooemqqALJ@mail.gmail.com> (raw)
In-Reply-To: <AANLkTinRJQM+Yky_ORVnf3i7Aq2CiUTvchQDxiR4D636@mail.gmail.com>

On Fri, Jul 30, 2010 at 01:10, Jim Cromie <jim.cromie@gmail.com> wrote:
> Hi Mulyadi,
>
> Youre a regular here, and would have some "authority" on making recommendations.

Oh please, I am just ordinary member :)

Uhm, maybe someone should contact Rik and talk about it. Or, at least,
everybody write their own mistakes when dealing with kernel dev on
their blog...that way, at least it is documented. So when the time
comes, it would simply be links to them.

Maybe just a simple idea that pops from my head...

-- 
regards,

Mulyadi Santosa
Freelance Linux trainer and consultant

blog: the-hydra.blogspot.com
training: mulyaditraining.blogspot.com

  reply	other threads:[~2010-07-29 20:23 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
2010-07-29 17:52         ` Mulyadi Santosa
2010-07-29 18:10       ` Jim Cromie
2010-07-29 20:23         ` Mulyadi Santosa [this message]
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='AANLkTikcjw=xgCM73cenoxS9=oUM6jshtn=ooemqqALJ@mail.gmail.com' \
    --to=mulyadi.santosa@gmail.com \
    --cc=bala1486@gmail.com \
    --cc=jim.cromie@gmail.com \
    --cc=kernelnewbies@nl.linux.org \
    --cc=linux-c-programming@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;
as well as URLs for NNTP newsgroup(s).