From: Nicolas Schier <nicolas@fjasle.eu>
To: Masahiro Yamada <masahiroy@kernel.org>
Cc: Arnd Bergmann <arnd@kernel.org>, Jonathan Corbet <corbet@lwn.net>,
Arnd Bergmann <arnd@arndb.de>,
Javier Martinez Canillas <javierm@redhat.com>,
Sakari Ailus <sakari.ailus@linux.intel.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] [v2] Documentation: kbuild: explain handling optional dependencies
Date: Thu, 15 Feb 2024 14:51:14 +0100 [thread overview]
Message-ID: <Zc4W0lXFq7xysTF4@bergen.fjasle.eu> (raw)
In-Reply-To: <CAK7LNAT2DNE3RMLdXhLbSRHz6nfuP825UK39sQHkJW4x+OyfVg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1364 bytes --]
On Thu 15 Feb 2024 22:40:46 GMT, Masahiro Yamada wrote:
> On Thu, Feb 15, 2024 at 9:39 PM Nicolas Schier <nicolas@fjasle.eu>
> wrote:
> >
> > On Mon 25 Sep 2023 16:06:41 GMT, Masahiro Yamada wrote:
> > > On Mon, Sep 18, 2023 at 4:20 AM Arnd Bergmann <arnd@kernel.org>
> > > wrote:
> > > >
> > > > From: Arnd Bergmann <arnd@arndb.de>
> > > >
> > > > This problem frequently comes up in randconfig testing, with
> > > > drivers failing to link because of a dependency on an optional
> > > > feature.
> > > >
> > > > The Kconfig language for this is very confusing, so try to
> > > > document it in "Kconfig hints" section.
> > > >
> > > > Reviewed-by: Javier Martinez Canillas <javierm@redhat.com>
> > > > Reviewed-by: Sakari Ailus <sakari.ailus@linux.intel.com>
> > > > Reviewed-by: Nicolas Schier <nicolas@fjasle.eu>
> > > > Signed-off-by: Arnd Bergmann <arnd@arndb.de>
> > > > ---
> > > > v2: fix typos pointed out by Nicolas Schier
> > >
> > >
> > > Applied to linux-kbuild. Thanks.
> >
> > Hi Masahiro,
> >
> > this patch seems to got lost, or did you intentionally removed it
> > again?
> >
> > Kind regards,
> > Nicolas
>
>
>
> Oh?
>
> I can see it in the mainline.
ups, I'm sorry for the noise. You are right, I had an heavily
out-dated tree at hand and wasn't aware of it ...
Kind regards,
Nicolas
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2024-02-15 13:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-17 19:19 [PATCH] [v2] Documentation: kbuild: explain handling optional dependencies Arnd Bergmann
2023-09-25 7:06 ` Masahiro Yamada
2024-02-15 12:38 ` Nicolas Schier
2024-02-15 13:40 ` Masahiro Yamada
2024-02-15 13:51 ` Nicolas Schier [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=Zc4W0lXFq7xysTF4@bergen.fjasle.eu \
--to=nicolas@fjasle.eu \
--cc=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=sakari.ailus@linux.intel.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 read-only IMAP folder(s) and NNTP newsgroup(s).