From: "Arnd Bergmann" <arnd@arndb.de>
To: "Nicolas Schier" <nicolas@fjasle.eu>
Cc: "Arnd Bergmann" <arnd@kernel.org>,
"Masahiro Yamada" <masahiroy@kernel.org>,
"Jonathan Corbet" <corbet@lwn.net>,
"Sakari Ailus" <sakari.ailus@iki.fi>,
"Javier Martinez Canillas" <javierm@redhat.com>,
"Nathan Chancellor" <nathan@kernel.org>,
"Nick Desaulniers" <ndesaulniers@google.com>,
linux-kbuild@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Documentation: kbuild: explain handling optional dependencies
Date: Thu, 14 Sep 2023 07:05:31 +0200 [thread overview]
Message-ID: <82dfa2eb-1867-4cdc-b7b8-918d426575ed@app.fastmail.com> (raw)
In-Reply-To: <ZQKDRANlIWGqTA/9@bergen.fjasle.eu>
On Thu, Sep 14, 2023, at 05:51, Nicolas Schier wrote:
> On Wed 13 Sep 2023 23:16:47 GMT, Arnd Bergmann wrote:
>> On Wed, Sep 13, 2023, at 22:34, Nicolas Schier wrote:
>> >
>> > BAR=y => FOO={N/m/y}
>> > BAR=m => FOO is not selectable
>> > BAR=n => FOO={N/m/y}
>>
>> That is indeed the point: if BAR=m, we want to be able to pick FOO=m
>> here, otherwise it is impossible to enabled everything as modules.
>
> oh, I misinterpreted your very first sentence; thanks for clarifying it to me
> and sorry for the noise.
> With the minor fixes:
>
> Reviewed-by: Nicolas Schier <nicolas@fjasle.eu>
>
Ok, thanks!
I understand that the text is still confusing, so if anyone has an
idea for how to improve it further, let me know, otherwise
I'll send what I have now with type fixes as v2.
Arnd
next prev parent reply other threads:[~2023-09-14 5:05 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-13 11:37 [PATCH] Documentation: kbuild: explain handling optional dependencies Arnd Bergmann
2023-09-13 14:25 ` Javier Martinez Canillas
2023-09-13 16:11 ` Sakari Ailus
2023-09-13 19:48 ` Nicolas Schier
2023-09-13 19:55 ` Arnd Bergmann
2023-09-13 20:34 ` Nicolas Schier
2023-09-13 21:16 ` Arnd Bergmann
2023-09-14 3:51 ` Nicolas Schier
2023-09-14 5:05 ` Arnd Bergmann [this message]
2023-09-14 3:56 ` Javier Martinez Canillas
2023-09-14 17:07 ` Masahiro Yamada
2023-09-14 13:42 ` Jani Nikula
2023-09-14 14:57 ` Arnd Bergmann
2023-09-14 15:56 ` Jani Nikula
2023-09-14 17:23 ` Masahiro Yamada
2023-09-15 5:26 ` Arnd Bergmann
2023-09-15 7:34 ` Jani Nikula
2023-09-15 7:44 ` Arnd Bergmann
2023-09-15 15:48 ` Randy Dunlap
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=82dfa2eb-1867-4cdc-b7b8-918d426575ed@app.fastmail.com \
--to=arnd@arndb.de \
--cc=arnd@kernel.org \
--cc=corbet@lwn.net \
--cc=javierm@redhat.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=nicolas@fjasle.eu \
--cc=sakari.ailus@iki.fi \
/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