From: "loïc tourlonias" <loic.tourlonias@gmail.com>
To: "Tobin C. Harding" <me@tobin.cc>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
driverdev-devel@linuxdriverproject.org,
Dan Carpenter <dan.carpenter@oracle.com>,
Kernelnewbies <kernelnewbies@kernelnewbies.org>
Subject: Re: [OSSNA] Intro to kernel hacking tutorial
Date: Fri, 5 Jul 2019 09:48:41 +0200 [thread overview]
Message-ID: <CA+XxOSFtCyg7N8DAxyv-aqSRhMHy9hbTaaajmQe2fvW==rkJUQ@mail.gmail.com> (raw)
In-Reply-To: <20190705025055.GA7037@ares>
Hi,
On Fri, Jul 5, 2019 at 4:51 AM Tobin C. Harding <me@tobin.cc> wrote:
>
> Hi,
>
> I am doing a tutorial at OSSNA in San Diego on getting into kernel
> hacking. I'm only a couple of years deep into kernel hacking so I
> wanted to reach out to those more experienced than myself (and those
> less experienced).
>
> Is there any thing that you would really like to see covered in this
> tutorial?
>
I'm not involved in kernel hacking, but I've tried several times to
start writing patches. Because of time sharing issue I haven't get to
the end but a tutorial will be great.
The question I've asked me during my several tries is where can I be
useful (which topics, what I'm confident enough in to play with...).
Looking in drivers/staging wasn't any help in my case and making
kernel janitor is useful but not very well viewed as I've heard.
So I think that digging further in your tutorial on several ways to
start kernel hacking may be interesting.
> Current format/content: the tutorial will attempt to bridge the gap in
> the learning process between the 'first patch' page on kernelnewbies.org
> wiki and being 'comfortable' patching the kernel via LKML. Outcome will
> (hopefully) be a small patch set into drivers/staging/. (Don't worry
> Greg only one group got to this stage last time, you won't get flooded
> with patches :)
>
HTH and very enthusiast to read this tutorial.
Loïc
> Thanks,
> Tobin.
>
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies@kernelnewbies.org
> https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
_______________________________________________
devel mailing list
devel@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
WARNING: multiple messages have this Message-ID (diff)
From: "loïc tourlonias" <loic.tourlonias@gmail.com>
To: "Tobin C. Harding" <me@tobin.cc>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
driverdev-devel@linuxdriverproject.org,
Dan Carpenter <dan.carpenter@oracle.com>,
Kernelnewbies <kernelnewbies@kernelnewbies.org>
Subject: Re: [OSSNA] Intro to kernel hacking tutorial
Date: Fri, 5 Jul 2019 09:48:41 +0200 [thread overview]
Message-ID: <CA+XxOSFtCyg7N8DAxyv-aqSRhMHy9hbTaaajmQe2fvW==rkJUQ@mail.gmail.com> (raw)
In-Reply-To: <20190705025055.GA7037@ares>
Hi,
On Fri, Jul 5, 2019 at 4:51 AM Tobin C. Harding <me@tobin.cc> wrote:
>
> Hi,
>
> I am doing a tutorial at OSSNA in San Diego on getting into kernel
> hacking. I'm only a couple of years deep into kernel hacking so I
> wanted to reach out to those more experienced than myself (and those
> less experienced).
>
> Is there any thing that you would really like to see covered in this
> tutorial?
>
I'm not involved in kernel hacking, but I've tried several times to
start writing patches. Because of time sharing issue I haven't get to
the end but a tutorial will be great.
The question I've asked me during my several tries is where can I be
useful (which topics, what I'm confident enough in to play with...).
Looking in drivers/staging wasn't any help in my case and making
kernel janitor is useful but not very well viewed as I've heard.
So I think that digging further in your tutorial on several ways to
start kernel hacking may be interesting.
> Current format/content: the tutorial will attempt to bridge the gap in
> the learning process between the 'first patch' page on kernelnewbies.org
> wiki and being 'comfortable' patching the kernel via LKML. Outcome will
> (hopefully) be a small patch set into drivers/staging/. (Don't worry
> Greg only one group got to this stage last time, you won't get flooded
> with patches :)
>
HTH and very enthusiast to read this tutorial.
Loïc
> Thanks,
> Tobin.
>
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies@kernelnewbies.org
> https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next prev parent reply other threads:[~2019-07-05 7:40 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-05 2:50 [OSSNA] Intro to kernel hacking tutorial Tobin C. Harding
2019-07-05 3:32 ` Amit Kumar
2019-07-05 3:32 ` Amit Kumar
2019-07-05 5:10 ` Amit Kumar
2019-07-05 5:10 ` Amit Kumar
2019-07-08 23:46 ` Tobin C. Harding
2019-07-05 7:48 ` loïc tourlonias [this message]
2019-07-05 7:48 ` loïc tourlonias
2019-07-19 9:36 ` Dan Carpenter
2019-07-19 9:36 ` Dan Carpenter
2019-07-22 9:29 ` Tobin C. Harding
2019-07-22 9:29 ` Tobin C. Harding
2019-09-01 0:00 ` Amit Kumar
2019-09-01 0:00 ` Amit Kumar
2019-09-02 1:51 ` Tobin C. Harding
2019-09-02 1:51 ` Tobin C. Harding
2019-09-02 6:29 ` Amit Kumar
2019-09-02 12:42 ` Anatoly Pugachev
2019-09-02 12:42 ` Anatoly Pugachev
2019-09-02 14:08 ` Valdis Klētnieks
2019-09-02 14:08 ` Valdis Klētnieks
2019-09-03 1:49 ` Tobin C. Harding
2019-09-03 1:49 ` Tobin C. Harding
2019-09-04 9:55 ` Anatoly Pugachev
2019-09-04 9:55 ` Anatoly Pugachev
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='CA+XxOSFtCyg7N8DAxyv-aqSRhMHy9hbTaaajmQe2fvW==rkJUQ@mail.gmail.com' \
--to=loic.tourlonias@gmail.com \
--cc=dan.carpenter@oracle.com \
--cc=driverdev-devel@linuxdriverproject.org \
--cc=gregkh@linuxfoundation.org \
--cc=kernelnewbies@kernelnewbies.org \
--cc=me@tobin.cc \
/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.