linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Jean Delvare <jdelvare@suse.com>,
	Eric Tremblay <etremblay@distech-controls.com>,
	linux-hwmon@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] hwmon: gpio-fan: mark OF related data as maybe unused
Date: Sun, 12 Mar 2023 22:14:44 +0100	[thread overview]
Message-ID: <92fc2b5e-05fe-4f69-916c-82795b0d0db2@linaro.org> (raw)
In-Reply-To: <062a2834-ece9-49ed-0e15-30730b65ef50@roeck-us.net>

On 12/03/2023 22:03, Guenter Roeck wrote:
>>
>> The driver would not built. I mean, I did not cheat here to built it
>> with incorrect config.
>>
>> I rather suspect that config is broken due to:
>> WARNING: unmet direct dependencies detected for OF_GPIO
>> WARNING: unmet direct dependencies detected for GPIO_SYSCON
>> WARNING: unmet direct dependencies detected for MFD_STMFX
>>
>> This was next-20230308
>>
> Interesting. That has been fixed in next-20230310, where
> SENSORS_GPIO_FAN is again deselected if CONFIG_OF is disabled.

Nice, I picked by coincidence lucky base :)

Best regards,
Krzysztof


      reply	other threads:[~2023-03-12 21:14 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-11 11:16 [PATCH 1/2] hwmon: gpio-fan: mark OF related data as maybe unused Krzysztof Kozlowski
2023-03-11 11:16 ` [PATCH 2/2] hwmon: tmp512: " Krzysztof Kozlowski
2023-03-12 18:10   ` Guenter Roeck
2023-03-12 18:00 ` [PATCH 1/2] hwmon: gpio-fan: " Guenter Roeck
2023-03-12 18:06 ` Guenter Roeck
2023-03-12 18:08   ` Krzysztof Kozlowski
2023-03-12 18:48     ` Guenter Roeck
2023-03-12 19:32       ` Krzysztof Kozlowski
2023-03-12 21:03         ` Guenter Roeck
2023-03-12 21:14           ` Krzysztof Kozlowski [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=92fc2b5e-05fe-4f69-916c-82795b0d0db2@linaro.org \
    --to=krzysztof.kozlowski@linaro.org \
    --cc=etremblay@distech-controls.com \
    --cc=jdelvare@suse.com \
    --cc=linux-hwmon@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    /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).