From: "rpjday@crashcourse.ca" <rpjday@crashcourse.ca>
To: YP docs mailing list <docs@lists.yoctoproject.org>
Subject: "KBUILD_DEFCONFIG" description in kernel-dev manual seems wrong
Date: Thu, 20 Feb 2020 03:53:35 -0500 (EST) [thread overview]
Message-ID: <alpine.LFD.2.21.2002200346570.15458@localhost.localdomain> (raw)
in current kernel-dev manual, section on "in-tree" defconfig file:
https://www.yoctoproject.org/docs/current/kernel-dev/kernel-dev.html#using-an-in-tree-defconfig-file
the example given is:
KBUILD_DEFCONFIG_common-pc ?= "/home/scottrif/configfiles/my_defconfig_file"
but that's not an "in-tree" file, is it? i thought that variable
referred to just the file name within an existing kernel source tree,
no? the processing in kernel-yocto.bbclass certainly suggests that:
if [ -f "${S}/arch/${ARCH}/configs/${KBUILD_DEFCONFIG}" ]; then
should i submit a patch for that? perhaps steal the example from the
reference manual:
KBUILD_DEFCONFIG_raspberrypi2 = "bcm2709_defconfig"
rday
next reply other threads:[~2020-02-20 8:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-20 8:53 rpjday [this message]
2020-02-20 13:05 ` [docs] "KBUILD_DEFCONFIG" description in kernel-dev manual seems wrong Bruce Ashfield
2020-02-20 13:19 ` rpjday
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=alpine.LFD.2.21.2002200346570.15458@localhost.localdomain \
--to=rpjday@crashcourse.ca \
--cc=docs@lists.yoctoproject.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.