All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Tobin C. Harding" <me@tobin.cc>
To: "Valdis Klētnieks" <valdis.kletnieks@vt.edu>
Cc: Kernelnewbies <kernelnewbies@kernelnewbies.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	driverdev-devel@linuxdriverproject.org,
	Anatoly Pugachev <matorola@gmail.com>,
	Amit Kumar <free.amit.kumar@gmail.com>,
	Dan Carpenter <dan.carpenter@oracle.com>
Subject: Re: [OSSNA] Intro to kernel hacking tutorial
Date: Tue, 3 Sep 2019 11:49:42 +1000	[thread overview]
Message-ID: <20190903014942.GA30045@ares> (raw)
In-Reply-To: <490137.1567433334@turing-police>


[-- Attachment #1.1: Type: text/plain, Size: 803 bytes --]

On Mon, Sep 02, 2019 at 10:08:54AM -0400, Valdis Klētnieks wrote:
> On Mon, 02 Sep 2019 15:42:19 +0300, Anatoly Pugachev said:
> 
> > is it intentionally that you use
> >
> > yes "" | make oldconfig
> >
> > instead of
> >
> > make olddefconfig
> 
> They do something different.  'olddefconfig' just takes the platform or
> architecture defconfig and updates it for any new CONFIG_* variables added
> since the last time the defconfig was updated in the tree.
> 
> yes "" | make oldconfig  does the same updating for new CONFIG_* variables, but
> starts with the most recent .config - which produces wildly different results
> if the .config had previously been minimized by 'make localmodconfig' or other
> similar techniques.

Thanks Valdis, you're the man!


       Tobin



[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

[-- Attachment #2: Type: text/plain, Size: 170 bytes --]

_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

  reply	other threads:[~2019-09-03  1:50 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
2019-09-02 14:08           ` Valdis Klētnieks
2019-09-03  1:49             ` Tobin C. Harding [this message]
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=20190903014942.GA30045@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 \
    --cc=matorola@gmail.com \
    --cc=valdis.kletnieks@vt.edu \
    /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.