From: chambilkethakur@gmail.com (Anuz Pratap Singh Tomar)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Open to work for any kernel module
Date: Thu, 26 Apr 2012 10:46:13 +0100 [thread overview]
Message-ID: <CAJnfX5sGGP=86BX-aDthfS+G4pA94skcNuFsT6OeTRv7dqsC1Q@mail.gmail.com> (raw)
In-Reply-To: <CAEjcey0amkK6OUPfteHXHtkQT_ibskK2qBMFp8TWZ0X9oo+QSg@mail.gmail.com>
On Thu, Apr 26, 2012 at 2:18 AM, Anil Varma Biruduraju <
anilvarma87@gmail.com> wrote:
> Hi Anuz,
>
> Thanks for the reply..
>
> I looked at the Kernel janitors web link but dont know
> where to start I see coding standards and wondering what to do...
>
> I know I might me asking a lot but can you please let
> to know where to start and whom to contact first..
>
> Thank you
>
> there is a kernel janitor mailing list,
also try looking for kernel bugs at kernel bugzilla, you may find something
interesting: https://bugzilla.kernel.org
> Regards,
> Anil Varma B.
>
> On Mon, Apr 23, 2012 at 4:27 AM, Anuz Pratap Singh Tomar
> <chambilkethakur@gmail.com> wrote:
> >
> >
> > On Mon, Apr 23, 2012 at 6:12 AM, Anil Varma Biruduraju
> > <anilvarma87@gmail.com> wrote:
> >>
> >> Hi All,
> >>
> >> Please let me know if I can start working on some
> >> kernel modules.
> >> Thank you.
> >>
> > Try to look up in kernel janitors.
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20120426/458dd11f/attachment.html
prev parent reply other threads:[~2012-04-26 9:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-23 5:12 Open to work for any kernel module Anil Varma Biruduraju
2012-04-23 9:27 ` Anuz Pratap Singh Tomar
[not found] ` <CAEjcey0amkK6OUPfteHXHtkQT_ibskK2qBMFp8TWZ0X9oo+QSg@mail.gmail.com>
2012-04-26 9:46 ` Anuz Pratap Singh Tomar [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='CAJnfX5sGGP=86BX-aDthfS+G4pA94skcNuFsT6OeTRv7dqsC1Q@mail.gmail.com' \
--to=chambilkethakur@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.