All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Saravana Kannan <saravanak@google.com>
Cc: Michael Walle <michael@walle.cc>,
	Geert Uytterhoeven <geert+renesas@glider.be>,
	Ulf Hansson <ulf.hansson@linaro.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	kernelci-results@groups.io, bot@kernelci.org,
	gtucker@collabora.com, linux-arm-kernel@lists.infradead.org,
	linux-pci@vger.kernel.org
Subject: Re: next/master bisection: baseline.bootrr.intel-igb-probed on kontron-pitx-imx8m
Date: Tue, 16 Aug 2022 18:26:02 +0100	[thread overview]
Message-ID: <YvvTKkR4sOIsFxA4@sirena.org.uk> (raw)
In-Reply-To: <CAGETcx_JSViBcySNp+Rany2osBiKL7ON+tooPKW8TOTP6+t_HA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 882 bytes --]

On Fri, Aug 12, 2022 at 04:54:25PM -0700, Saravana Kannan wrote:

> While you are here, I'm working towards patches on top of [1] where
> fw_devlink will tie the sync_state() callback to each regulator. Also,
> i realized that if you can convert the regulator_class to a
> regulator_bus, we could remove a lot of the "find the supply for this
> regulator when it's registered" code and let device links handle it.
> Let me know if that's something you'd be okay with. It would change
> the sysfs path for /sys/class/regulator and moves it to
> /sys/bus/regulator, but not sure if that's considered an ABI breakage
> (sysfs paths change all the time).

That *does* sound like it'd be an ABI issue TBH.  I thought there was
support for keeping class around even when converting to a bus (though
TBH given how entirely virtual this stuff us it seems odd that we'd be
going for a bus).

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

WARNING: multiple messages have this Message-ID (diff)
From: Mark Brown <broonie@kernel.org>
To: Saravana Kannan <saravanak@google.com>
Cc: Michael Walle <michael@walle.cc>,
	Geert Uytterhoeven <geert+renesas@glider.be>,
	Ulf Hansson <ulf.hansson@linaro.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	kernelci-results@groups.io, bot@kernelci.org,
	gtucker@collabora.com, linux-arm-kernel@lists.infradead.org,
	linux-pci@vger.kernel.org
Subject: Re: next/master bisection: baseline.bootrr.intel-igb-probed on kontron-pitx-imx8m
Date: Tue, 16 Aug 2022 18:26:02 +0100	[thread overview]
Message-ID: <YvvTKkR4sOIsFxA4@sirena.org.uk> (raw)
In-Reply-To: <CAGETcx_JSViBcySNp+Rany2osBiKL7ON+tooPKW8TOTP6+t_HA@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 882 bytes --]

On Fri, Aug 12, 2022 at 04:54:25PM -0700, Saravana Kannan wrote:

> While you are here, I'm working towards patches on top of [1] where
> fw_devlink will tie the sync_state() callback to each regulator. Also,
> i realized that if you can convert the regulator_class to a
> regulator_bus, we could remove a lot of the "find the supply for this
> regulator when it's registered" code and let device links handle it.
> Let me know if that's something you'd be okay with. It would change
> the sysfs path for /sys/class/regulator and moves it to
> /sys/bus/regulator, but not sure if that's considered an ABI breakage
> (sysfs paths change all the time).

That *does* sound like it'd be an ABI issue TBH.  I thought there was
support for keeping class around even when converting to a bus (though
TBH given how entirely virtual this stuff us it seems odd that we'd be
going for a bus).

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

[-- Attachment #2: Type: text/plain, Size: 176 bytes --]

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2022-08-16 17:26 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <62eed399.170a0220.2503a.1c64@mx.google.com>
2022-08-08 12:22 ` next/master bisection: baseline.bootrr.intel-igb-probed on kontron-pitx-imx8m Mark Brown
2022-08-08 12:22   ` Mark Brown
2022-08-08 12:31   ` Michael Walle
2022-08-08 12:31     ` Michael Walle
2022-08-08 12:35   ` Michael Walle
2022-08-08 12:35     ` Michael Walle
2022-08-08 12:41     ` Mark Brown
2022-08-08 12:41       ` Mark Brown
2022-08-12 23:54       ` Saravana Kannan
2022-08-12 23:54         ` Saravana Kannan
2022-08-16 17:26         ` Mark Brown [this message]
2022-08-16 17:26           ` Mark Brown
2022-08-16 17:48           ` Saravana Kannan
2022-08-16 17:48             ` Saravana Kannan
2022-08-16 17:53             ` Mark Brown
2022-08-16 17:53               ` Mark Brown
2022-08-16 18:04               ` Saravana Kannan
2022-08-16 18:04                 ` Saravana Kannan
2022-08-17  6:44             ` Greg Kroah-Hartman
2022-08-17  6:44               ` Greg Kroah-Hartman
2022-08-17 12:58               ` Mark Brown
2022-08-17 12:58                 ` Mark Brown
2022-08-12 19:29   ` [REGRESSION] " Bjorn Helgaas
2022-08-12 19:29     ` Bjorn Helgaas
2022-08-12 23:48     ` Saravana Kannan
2022-08-12 23:48       ` Saravana Kannan
     [not found] <63f141b2.170a0220.57e67.6c7c@mx.google.com>
2023-02-20 18:10 ` Mark Brown
2023-02-20 18:10   ` Mark Brown
2023-02-20 18:38   ` Michael Walle
2023-02-20 18:38     ` Michael Walle

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=YvvTKkR4sOIsFxA4@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=bot@kernelci.org \
    --cc=geert+renesas@glider.be \
    --cc=gregkh@linuxfoundation.org \
    --cc=gtucker@collabora.com \
    --cc=kernelci-results@groups.io \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=michael@walle.cc \
    --cc=saravanak@google.com \
    --cc=ulf.hansson@linaro.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.