From: "Tobin C. Harding" <me@tobin.cc>
To: Amit Kumar <free.amit.kumar@gmail.com>
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: Tue, 9 Jul 2019 09:46:01 +1000 [thread overview]
Message-ID: <20190708234601.GB18120@ares> (raw)
In-Reply-To: <CAPTh4OuKv4Fx2DOWygCO0oXAm8xLw2f47igrnvhDEf2HWWyuEA@mail.gmail.com>
On Fri, Jul 05, 2019 at 10:40:43AM +0530, Amit Kumar wrote:
> On Fri, Jul 5, 2019 at 9:02 AM Amit Kumar <free.amit.kumar@gmail.com> wrote:
> >
> > On Fri, Jul 5, 2019 at 8:21 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?
> > >
> > > If you are a grey beard is there anything that you have been lamenting
> > > us newbies not knowing/doing?
> > >
> > > If you are a newbie is there anything that you are struggling with that
> > > you really want to learn?
> > Thank you.
> > Where can I find your tutorial?
It's not written yet :)
> I forget to tell, merely creating and sending patches is not important.
> Also I would like to know how to manage patches, using git, mutt, quilt
> and so on.
> Sending patch through git-email is good. But different versions of patch.
> Applying patch from mutt. Replying to patch recipients.
Nice suggestions thanks, will work this in.
thanks,
Tobin.
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next prev parent reply other threads:[~2019-07-08 23:46 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 [this message]
2019-07-05 7:48 ` loïc tourlonias
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=20190708234601.GB18120@ares \
--to=me@tobin.cc \
--cc=dan.carpenter@oracle.com \
--cc=driverdev-devel@linuxdriverproject.org \
--cc=free.amit.kumar@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=kernelnewbies@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.