From: Robert Gadsdon <rhgadsdon@gmail.com>
To: linux-kbuild@vger.kernel.org
Cc: Masahiro Yamada <yamada.masahiro@socionext.com>,
Ulf Magnusson <ulfalizer@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] kconfig: fix 'Save As' menu of xconfig
Date: Mon, 6 May 2019 12:10:21 -0700 [thread overview]
Message-ID: <84db9131-5498-d2d5-a984-11079e3c2a6e@gmail.com> (raw)
In-Reply-To: <1552234395-7699-1-git-send-email-yamada.masahiro@socionext.com>
On 03/10/2019 09:13 AM, Masahiro Yamada wrote:
> The 'Save As' menu of xconfig is not working; it always saves the
> kernel configuration into the default file irrespective of the file
> chosen in the dialog box.
>
> The 'Save' menu always writes into the default file, but it would
> make more sense to write into the file previously chosen by 'Load'
> or 'Save As'.
>
> Signed-off-by: Masahiro Yamada<yamada.masahiro@socionext.com>
> ---
The 'save as' may be used for out-of-tree kernel config saves, but the
default 'save' should always save to the in-tree .config file, as before
(and for the past 10+ years..) If the kernel config was loaded from an
out-of-tree location, it now saves back to that out-of-tree location,
which is useless for the kernel compile..
I have always kept my hardware/system-specific kernel configs
out-of-tree, and then applied them in-tree before compiling.
Now, I have to use 'save as' and type in the entire in-tree path
(/usr/src/linux-5.1/.config) each time, in order to apply the specific
config to the kernel, ready for compilation.
Robert Gadsdon.
rglinuxtech.com
next prev parent reply other threads:[~2019-05-06 19:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-10 16:13 Masahiro Yamada
2019-05-06 19:10 ` Robert Gadsdon [this message]
2019-05-07 3:01 ` Masahiro Yamada
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=84db9131-5498-d2d5-a984-11079e3c2a6e@gmail.com \
--to=rhgadsdon@gmail.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ulfalizer@gmail.com \
--cc=yamada.masahiro@socionext.com \
/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
all inboxes | Powered by JetHome®