All of lore.kernel.org
 help / color / mirror / Atom feed
From: bhat.srivatsa@gmail.com (Srivatsa Bhat)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Iterating through all the processes in a module
Date: Thu, 23 Feb 2012 16:42:51 +0530	[thread overview]
Message-ID: <CAC_BnSUPCRpdL3E7ZZSh0xG3K1b9w9KR9-uc2=uk4HQ2BYmH0Q@mail.gmail.com> (raw)
In-Reply-To: <20120222145309.GA25682@kroah.com>

On Wed, Feb 22, 2012 at 8:23 PM, Greg KH <greg@kroah.com> wrote:

>
> A: No.
> Q: Should I include quotations after my reply?
>
> http://daringfireball.net/2007/07/on_top
>
> On Wed, Feb 22, 2012 at 02:07:22PM +0100, Arokux B. wrote:
> > Dear Greg,
> >
> > thank you very much for your quick reply.
> >
> > Having my code as a module I can trigger its execution (load a module)
> > and disable it (unload a module). How can I achieve this if the code
> > is inside the kernel? One possibility I see is adding an entry in the
> > procfs.
>
> I don't see what procfs has to do with this, please explain.
>
> And as you said this was for "learning purposes", then just build it
> into the kernel, there's no need for it to be a module.
>
>
Heh, you can just put back the relevant parts of what commit
c59923a15c12d2b3597af913bf234a0ef264a38b removed and then do what
you want as a module, if it is for learning purposes :-)

Regards,
Srivatsa S. Bhat
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20120223/52b52959/attachment.html 

  reply	other threads:[~2012-02-23 11:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-07 17:45 Iterating through all the processes in a module Arokux B.
2012-02-07 19:17 ` Greg KH
2012-02-22 13:07   ` Arokux B.
2012-02-22 14:53     ` Greg KH
2012-02-23 11:12       ` Srivatsa Bhat [this message]
2012-02-22 15:30     ` Ezequiel García
2012-02-22 16:43       ` Javier Martinez Canillas
2012-02-23 11:07         ` Arokux B.

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='CAC_BnSUPCRpdL3E7ZZSh0xG3K1b9w9KR9-uc2=uk4HQ2BYmH0Q@mail.gmail.com' \
    --to=bhat.srivatsa@gmail.com \
    --cc=kernelnewbies@lists.kernelnewbies.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 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.