From: Jonathan Corbet <corbet@lwn.net>
To: Ismael Luceno <ismael@iodev.co.uk>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
Ismael Luceno <ismael@iodev.co.uk>,
Thorsten Leemhuis <linux@leemhuis.info>
Subject: Re: [PATCH] docs: reporting-issues: Remove reference to oldnoconfig
Date: Wed, 31 Mar 2021 14:34:40 -0600 [thread overview]
Message-ID: <87im57jc4f.fsf@meer.lwn.net> (raw)
In-Reply-To: <20210331163541.28356-1-ismael@iodev.co.uk>
Ismael Luceno <ismael@iodev.co.uk> writes:
> Replace it with olddefconfig. oldnoconfig didn't do what the document
> suggests (it aliased to olddefconfig), and isn't available since 4.19.
>
> Ref: 04c459d20448 ("kconfig: remove oldnoconfig target")
> Ref: 312ee68752fa ("kconfig: announce removal of oldnoconfig if used")
> Signed-off-by: Ismael Luceno <ismael@iodev.co.uk>
> ---
> Documentation/admin-guide/reporting-issues.rst | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/Documentation/admin-guide/reporting-issues.rst b/Documentation/admin-guide/reporting-issues.rst
> index 07879d01fe68..ffa0d4c6e450 100644
> --- a/Documentation/admin-guide/reporting-issues.rst
> +++ b/Documentation/admin-guide/reporting-issues.rst
> @@ -1000,8 +1000,7 @@ In the whole process keep in mind: an issue only qualifies as regression if the
> older and the newer kernel got built with a similar configuration. The best way
> to archive this: copy the configuration file (``.config``) from the old working
> kernel freshly to each newer kernel version you try. Afterwards run ``make
> -oldnoconfig`` to adjust it for the needs of the new version without enabling
> -any new feature, as those are allowed to cause regressions.
> +olddefconfig`` to adjust it for the needs of the new version.
[CC += Thorsten]
Applied, thanks.
jon
prev parent reply other threads:[~2021-03-31 20:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-31 16:35 [PATCH] docs: reporting-issues: Remove reference to oldnoconfig Ismael Luceno
2021-03-31 20:34 ` Jonathan Corbet [this message]
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=87im57jc4f.fsf@meer.lwn.net \
--to=corbet@lwn.net \
--cc=ismael@iodev.co.uk \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@leemhuis.info \
/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.