From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Thorsten Leemhuis <linux@leemhuis.info>,
Jonathan Corbet <corbet@lwn.net>
Cc: Randy Dunlap <rdunlap@infradead.org>,
Lukas Bulwahn <lukas.bulwahn@gmail.com>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
regressions@lists.linux.dev
Subject: Re: [PATCH v3] docs: describe how to quickly build a trimmed kernel
Date: Tue, 7 Mar 2023 09:57:57 +0700 [thread overview]
Message-ID: <2d1362fd-c109-1d8f-5954-3d60475ed907@gmail.com> (raw)
In-Reply-To: <b12d433e-62ea-3ac4-dd97-be0288f1335f@leemhuis.info>
On 3/6/23 16:07, Thorsten Leemhuis wrote:
>> I think it depends whether someone would pick from /proc/config.gz or
>> /boot/config. My kernel configuration have CONFIG_IKCONFIG=y but I
>> often copy the config from the latter instead, since I booted with
>> arbitrary kernel version when compiling two or three versions, and I
>> want to ensure that the config used is from correct version (i.e.
>> I use /boot/config-5.15.x-string to build 5.15.x+1 kernel).
>
> Well, I'd say for most users the file that was automatically picked up
> by olddefconfig/localmodconfig will be the right one. And for cases like
> yours there is already this in the text:
>
> ```
> The make targets try to find the configuration for your running kernel
> automatically, but might choose poorly. A line like ‘# using defaults
> found in /boot/config-6.0.7-250.fc36.x86_64’ or ‘using config:
> ‘/boot/config-6.0.7-250.fc36.x86_64’ tells you which file they picked.
> If that is not the intended one, simply store it as ‘~/linux/.config’
> before using these make targets.
> ```
>
Ah, I don't see that feature! Thanks anyway.
--
An old man doll... just what I always wanted! - Clara
next prev parent reply other threads:[~2023-03-07 2:58 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-05 13:04 [PATCH v3] docs: describe how to quickly build a trimmed kernel Thorsten Leemhuis
2023-03-06 4:14 ` Bagas Sanjaya
2023-03-06 6:03 ` Thorsten Leemhuis
2023-03-06 4:19 ` Bagas Sanjaya
2023-03-06 5:40 ` Thorsten Leemhuis
2023-03-06 8:57 ` Bagas Sanjaya
2023-03-06 9:07 ` Thorsten Leemhuis
2023-03-07 2:57 ` Bagas Sanjaya [this message]
2023-03-09 14:42 ` Greg KH
2023-03-14 18:35 ` Jonathan Corbet
2023-03-15 4:17 ` Bagas Sanjaya
2023-03-15 9:28 ` Thorsten Leemhuis
2023-03-16 18:27 ` Jonathan Corbet
2023-03-22 13:47 ` Thorsten Leemhuis
2023-03-23 17:24 ` Jonathan Corbet
2023-03-23 17:37 ` Thorsten Leemhuis
2023-03-23 18:08 ` Jonathan Corbet
2023-03-15 4:19 ` Bagas Sanjaya
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=2d1362fd-c109-1d8f-5954-3d60475ed907@gmail.com \
--to=bagasdotme@gmail.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@leemhuis.info \
--cc=lukas.bulwahn@gmail.com \
--cc=rdunlap@infradead.org \
--cc=regressions@lists.linux.dev \
/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).