mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
	linux-kernel@vger.kernel.org, Peter Rosin <peda@axentia.se>,
	Mark Brown <broonie@kernel.org>
Subject: Re: [GIT PULL] mux drivers improvements for v6.16
Date: Wed, 21 May 2025 17:25:14 +0200	[thread overview]
Message-ID: <a2a619f9-d6ca-419d-af11-e41b6ae59a48@kernel.org> (raw)
In-Reply-To: <a15a54e4-e6f2-4e63-9fc5-141d0e2b010b@kernel.org>

On 21/05/2025 14:19, Krzysztof Kozlowski wrote:
>>>>
>>>> ----------------------------------------------------------------
>>>> Andrew Davis (1):
>>>>       mux: mmio: Do not use syscon helper to build regmap
>>> I received LKP build error report for some specific configuration:
>>> https://lore.kernel.org/oe-kbuild-all/202505150312.dYbBqUhG-lkp@intel.com/
>>>
>>> I will send a follow up fix for that and then later updated pull
>>> request, if you do not pull it till that time.
>>
>> I've taken this now, do you have a fix somewhere?
> Fix is being discussed on the lists, because it exposes Kconfig circular
> dependency:
> 
> 1. The actual fix which also tries to break circular dependency:
> https://lore.kernel.org/all/20250515140555.325601-2-krzysztof.kozlowski@linaro.org/
> 
> 2. A better way to break circular dependency:
> https://lore.kernel.org/all/20250516141722.13772-1-afd@ti.com/

+Cc Mark Brown,

Above circular-dependency-break (2) was applied by Mark for v6.16-rc1:
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regmap.git/commit/?h=for-6.16&id=c5a219395b4e6312102a505bfe73aac8f8bada8c

This means that my fix for LKP build error, should come after. My
proposal is to live with the LKP build error till v6.16-rc1 and then
apply my fix. I just sent v2 of my fix for LKP build error:
https://lore.kernel.org/r/20250521152354.92720-2-krzysztof.kozlowski@linaro.org/

Best regards,
Krzysztof

      reply	other threads:[~2025-05-21 15:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-13 10:50 Krzysztof Kozlowski
2025-05-13 10:53 ` [PATCH PULL] w1: Avoid -Wflex-array-member-not-at-end warnings Krzysztof Kozlowski
2025-05-21 12:13   ` Greg Kroah-Hartman
2025-05-15 13:34 ` [GIT PULL] mux drivers improvements for v6.16 Krzysztof Kozlowski
2025-05-21 12:14   ` Greg Kroah-Hartman
2025-05-21 12:19     ` Krzysztof Kozlowski
2025-05-21 15:25       ` 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=a2a619f9-d6ca-419d-af11-e41b6ae59a48@kernel.org \
    --to=krzk@kernel.org \
    --cc=broonie@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peda@axentia.se \
    /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

all inboxes | Powered by JetHome®