From: Szilard Fabian <szfabian@bluemarch.art>
To: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
platform-driver-x86@vger.kernel.org, jwoithe@just42.net,
Hans de Goede <hdegoede@redhat.com>,
W_Armin@gmx.de
Subject: Re: [PATCH v4] platform/x86/fujitsu-laptop: Add battery charge control support
Date: Tue, 27 Feb 2024 12:04:30 +0000 [thread overview]
Message-ID: <Zd3PxsHQEOQrf-9I@bluemarch.art> (raw)
In-Reply-To: <a4b35e55-1f29-6c98-745c-df6896e49270@linux.intel.com>
On Tue, Feb 27, 2024 at 11:18:16AM +0100, Ilpo Järvinen wrote:
> Hi,
>
> Can you please take a look at the two build failures LKP has brought up.
> They looked like some depends on and/or select clauses missing from
> Kconfig.
Hi,
Modifying drivers/platform/x86/Kconfig to include `depends on ACPI_BATTERY`
in the FUJITSU_LAPTOP config block fixes the problem with gcc. I think this
should fix the problem with clang too.
I'll post v5 with that change in a moment.
Regards,
Szilard
next prev parent reply other threads:[~2024-02-27 12:04 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-29 16:36 [RFC PATCH] platform/x86/fujitsu-laptop: Add battery charge control support Szilard Fabian
2024-01-29 18:00 ` [RFC PATCH v2] " Szilard Fabian
2024-01-30 2:02 ` Armin Wolf
2024-02-03 0:17 ` Szilard Fabian
2024-02-05 17:07 ` Armin Wolf
2024-02-05 23:37 ` Jonathan Woithe
2024-02-07 2:32 ` [RFC PATCH v3] " Szilard Fabian
2024-02-07 8:57 ` Hans de Goede
2024-02-08 1:56 ` Szilard Fabian
2024-02-08 9:11 ` Hans de Goede
2024-02-15 11:34 ` Ilpo Järvinen
2024-02-15 20:12 ` Szilard Fabian
2024-02-16 9:27 ` Ilpo Järvinen
2024-02-15 20:31 ` [PATCH v4] " Szilard Fabian
2024-02-18 4:47 ` Jonathan Woithe
2024-02-19 12:06 ` Ilpo Järvinen
2024-02-27 10:18 ` Ilpo Järvinen
2024-02-27 12:04 ` Szilard Fabian [this message]
2024-02-27 12:05 ` [PATCH v5] " Szilard Fabian
2024-02-27 12:53 ` Ilpo Järvinen
2024-02-27 21:47 ` Jonathan Woithe
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=Zd3PxsHQEOQrf-9I@bluemarch.art \
--to=szfabian@bluemarch.art \
--cc=W_Armin@gmx.de \
--cc=hdegoede@redhat.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=jwoithe@just42.net \
--cc=linux-kernel@vger.kernel.org \
--cc=platform-driver-x86@vger.kernel.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 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.