From: Kashyap Chamarthy <kchamart@redhat.com>
To: Thomas Huth <thuth@redhat.com>
Cc: qemu-devel@nongnu.org, alex.bennee@linaro.org,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Daniel P. Berrangé" <berrange@redhat.com>
Subject: Re: [PATCH v2] docs: build-system: rename "default-configs" to "configs"
Date: Thu, 1 Jun 2023 10:17:08 +0200 [thread overview]
Message-ID: <ZHhUBHCHnx+2fNG+@pinwheel> (raw)
In-Reply-To: <740eaa77-a217-8272-2eb3-51df11764447@redhat.com>
On Wed, May 31, 2023 at 04:22:34PM +0200, Thomas Huth wrote:
> On 23/05/2023 15.31, Kashyap Chamarthy wrote:
> > Commit 812b31d3f9 (configs: rename default-configs to configs and
> > reorganise, 2021-07-07) did the rename.
> >
> > Reflect that update also in the documentation.
> >
> > Signed-off-by: Kashyap Chamarthy <kchamart@redhat.com>
> > ---
> > docs/devel/build-system.rst | 12 +++++------
> > docs/devel/kconfig.rst | 40 ++++++++++++++++++++-----------------
> > 2 files changed, 28 insertions(+), 24 deletions(-)
> >
> > diff --git a/docs/devel/build-system.rst b/docs/devel/build-system.rst
> > index 1894721743..20ebcc9ac6 100644
> > --- a/docs/devel/build-system.rst
> > +++ b/docs/devel/build-system.rst
> ...
> > @@ -457,7 +457,7 @@ Built by Meson:
> > TARGET-NAME is again the name of a system or userspace emulator. The
> > config-devices.mak file is automatically generated by make using the
> > scripts/make_device_config.sh program, feeding it the
> > - default-configs/$TARGET-NAME file as input.
> > + configs/$TARGET-NAME file as input.
>
> This hunk does not apply anymore - but I think it can simply be dropped now.
Just for my own clarity, which precise part do you suggest to be
dropped?
> > ``config-host.h``, ``$TARGET_NAME-config-target.h``, ``$TARGET_NAME-config-devices.h``
> > These files are used by source code to determine what features are
> > diff --git a/docs/devel/kconfig.rst b/docs/devel/kconfig.rst
> > index e3a544e463..73118e5106 100644
> > --- a/docs/devel/kconfig.rst
> > +++ b/docs/devel/kconfig.rst
> > @@ -38,11 +38,11 @@ originated in the Linux kernel, though it was heavily simplified and
> > the handling of dependencies is stricter in QEMU.
> > Unlike Linux, there is no user interface to edit the configuration, which
> > -is instead specified in per-target files under the ``default-configs/``
> > +is instead specified in per-target files under the ``configs/target/``
>
> I think the Kconfig-related files are rather the ones in configs/devices/ ,
> so I'd use that directory here instead.
I see, will fix.
> > directory of the QEMU source tree. This is because, unlike Linux,
> > -configuration and dependencies can be treated as a black box when building
> > -QEMU; the default configuration that QEMU ships with should be okay in
> > -almost all cases.
> > +configuration and dependencies can be treated as a black box when
> > +building QEMU; the default configuration that QEMU ships with should be
> > +okay in almost all cases.
>
> Why did you change the above three lines?
Oops. Accidental bad habit of re-wrapping text in a paragraph. (When
editing a plain text file I periodically hit "gq}" -`vim` shortcut to
re-wrap text.)
[...]
> > They sometimes have ``select`` directives to bring in other required
> > subsystems or buses. For example, ``AUX`` (the DisplayPort auxiliary
> > @@ -229,7 +231,8 @@ declares its dependencies in different ways:
> > cannot be started at all without it. It should be listed under
> > ``imply`` if (depending on the QEMU command line) the board may or
> > may not be started without it. Boards also default to false; they are
> > - enabled by the ``default-configs/*.mak`` for the target they apply to.
> > + enabled by the ``configs/targets/TARGETNAME-softmmu/*.mak`` for the
>
> Should be configs/devices/... here, too, I think.
Yep; noted. Will fix.
Thanks for the review.
--
/kashyap
next prev parent reply other threads:[~2023-06-01 8:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-23 13:31 [PATCH v2] docs: build-system: rename "default-configs" to "configs" Kashyap Chamarthy
2023-05-23 13:45 ` Kashyap Chamarthy
2023-05-31 14:22 ` Thomas Huth
2023-06-01 8:17 ` Kashyap Chamarthy [this message]
2023-06-01 9:12 ` Thomas Huth
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=ZHhUBHCHnx+2fNG+@pinwheel \
--to=kchamart@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=berrange@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.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;
as well as URLs for NNTP newsgroup(s).