From: Anatoly Pugachev <matorola@gmail.com>
To: "Tobin C. Harding" <me@tobin.cc>
Cc: Amit Kumar <free.amit.kumar@gmail.com>,
driverdev-devel@linuxdriverproject.org,
Kernelnewbies <kernelnewbies@kernelnewbies.org>,
Dan Carpenter <dan.carpenter@oracle.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [OSSNA] Intro to kernel hacking tutorial
Date: Mon, 2 Sep 2019 15:42:19 +0300 [thread overview]
Message-ID: <CADxRZqyBgDEiZaK5At2RoCHPNquRA6OWvFg2SU3TZ9hsqEs8rg@mail.gmail.com> (raw)
In-Reply-To: <20190902015137.GB14611@ares>
On Mon, Sep 2, 2019 at 4:52 AM Tobin C. Harding <me@tobin.cc> wrote:
>
> On Sun, Sep 01, 2019 at 05:30:23AM +0530, Amit Kumar wrote:
> > Hi,
> > I think now your tutorial should be ready.
>
> I do not understand what this means sorry. Is it a request for action?
> The tutorial was a couple of weeks ago now, here is a link to the
> material if that is what you were asking
>
> https://github.com/tcharding/kernel/tree/master/workshop
Tobin,
is it intentionally that you use
yes "" | make oldconfig
instead of
make olddefconfig
in some of your docs ? ( tutorial/cheat-sheet.rst , tutorial/trouble-shoot.rst )
Want me to create/submit PR on github with 'make olddefconfig' ?
Thanks.
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next prev parent reply other threads:[~2019-09-02 12:42 UTC|newest]
Thread overview: 14+ 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 5:10 ` Amit Kumar
2019-07-08 23:46 ` Tobin C. Harding
2019-07-05 7:48 ` loïc tourlonias
2019-07-19 9:36 ` Dan Carpenter
2019-07-22 9:29 ` Tobin C. Harding
2019-09-01 0:00 ` Amit Kumar
2019-09-02 1:51 ` Tobin C. Harding
2019-09-02 6:29 ` Amit Kumar
2019-09-02 12:42 ` Anatoly Pugachev [this message]
2019-09-02 14:08 ` Valdis Klētnieks
2019-09-03 1:49 ` Tobin C. Harding
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=CADxRZqyBgDEiZaK5At2RoCHPNquRA6OWvFg2SU3TZ9hsqEs8rg@mail.gmail.com \
--to=matorola@gmail.com \
--cc=dan.carpenter@oracle.com \
--cc=driverdev-devel@linuxdriverproject.org \
--cc=free.amit.kumar@gmail.com \
--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 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).