From: Lee Jones <lee@kernel.org>
To: "Pavel Machek" <pavel@ucw.cz>, "Lee Jones" <lee@kernel.org>,
"Daniel Thompson" <daniel.thompson@linaro.org>,
"Linus Walleij" <linus.walleij@linaro.org>,
"Arnd Bergmann" <arnd@arndb.de>,
"Duje Mihanović" <duje.mihanovic@skole.hr>
Cc: Flavio Suligoi <f.suligoi@asem.it>,
Hans de Goede <hdegoede@redhat.com>,
Jianhua Lu <lujianhua000@gmail.com>,
"Matthew Wilcox (Oracle)" <willy@infradead.org>,
Helge Deller <deller@gmx.de>, Jingoo Han <jingoohan1@gmail.com>,
Karel Balej <balejk@matfyz.cz>,
dri-devel@lists.freedesktop.org, linux-fbdev@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-leds@vger.kernel.org,
kernel test robot <lkp@intel.com>
Subject: Re: [PATCH v2 0/2] leds: expresswire: Fix dependencies
Date: Fri, 23 Feb 2024 15:54:11 +0000 [thread overview]
Message-ID: <170870365155.1722159.6291358322517617428.b4-ty@kernel.org> (raw)
In-Reply-To: <20240216-expresswire-deps-v2-0-8be59c4a75f5@skole.hr>
On Fri, 16 Feb 2024 22:15:42 +0100, Duje Mihanović wrote:
> LEDS_EXPRESSWIRE does not depend on NEW_LEDS in practice but still does
> in Kconfig. Fix up its Kconfig entry to reflect this and fix a Kconfig
> warning.
>
>
Applied, thanks!
[1/2] Revert "leds: Only descend into leds directory when CONFIG_NEW_LEDS is set"
commit: 7a28f9cf6b7c8cad760b4d4ee7f53231cd76d8e4
[2/2] leds: expresswire: don't depend on NEW_LEDS
commit: 8cd0da0634222ceb434281f3034ad773ddfe0f4f
--
Lee Jones [李琼斯]
prev parent reply other threads:[~2024-02-23 15:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-16 21:15 [PATCH v2 0/2] leds: expresswire: Fix dependencies Duje Mihanović
2024-02-16 21:15 ` [PATCH v2 1/2] Revert "leds: Only descend into leds directory when CONFIG_NEW_LEDS is set" Duje Mihanović
2024-02-16 21:15 ` [PATCH v2 2/2] leds: expresswire: don't depend on NEW_LEDS Duje Mihanović
2024-02-23 15:54 ` Lee Jones [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=170870365155.1722159.6291358322517617428.b4-ty@kernel.org \
--to=lee@kernel.org \
--cc=arnd@arndb.de \
--cc=balejk@matfyz.cz \
--cc=daniel.thompson@linaro.org \
--cc=deller@gmx.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=duje.mihanovic@skole.hr \
--cc=f.suligoi@asem.it \
--cc=hdegoede@redhat.com \
--cc=jingoohan1@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=lkp@intel.com \
--cc=lujianhua000@gmail.com \
--cc=pavel@ucw.cz \
--cc=willy@infradead.org \
/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).