public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Matti Vaittinen <mazziesaccount@gmail.com>
To: Conor Dooley <conor@kernel.org>
Cc: Matti Vaittinen <matti.vaittinen@fi.rohmeurope.com>,
	Lee Jones <lee@kernel.org>, Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Liam Girdwood <lgirdwood@gmail.com>,
	Mark Brown <broonie@kernel.org>,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 01/14] dt-bindings: regulator: Add ROHM BD96802 PMIC
Date: Wed, 9 Apr 2025 08:43:31 +0300	[thread overview]
Message-ID: <62f78786-f9db-4e05-9001-28b786df669b@gmail.com> (raw)
In-Reply-To: <b233f08a-ac8a-4670-8b32-8afc8a7dfc0c@gmail.com>

On 09/04/2025 07:30, Matti Vaittinen wrote:
> On 08/04/2025 19:16, Conor Dooley wrote:
>> On Tue, Apr 08, 2025 at 11:40:41AM +0300, Matti Vaittinen wrote:
>>> BD96802Qxx-C is an automotive grade configurable Power Management
>>> Integrated Circuit supporting Functional Safety features for application
>>> processors, SoCs and FPGAs. BD96802 is controlled via I2C, provides two
>>> interrupt lines and has two controllable buck regulators.
>>>
>>> The BD96802 belongs to the family of ROHM Scalable PMICs and is intended
>>> to be used as a companion PMIC for the BD96801.
>>>
>>> Signed-off-by: Matti Vaittinen <mazziesaccount@gmail.com>
>>
>> I think I acked this one on v1, no?
>> https://lore.kernel.org/all/20250326-candy-endocrine-2e7b2182e53b@spud/
> 
> Sorry Conor!
> Somehow I managed to drop your acks. Also from the other binding 
> patches.

Oh, actually, I didn't drop acks from the other bindings. Seems like it 
was just this one. Sorry for the confusion!

Anyways, all should have acks now - Thanks again for the reviews!

Yours,
	-- Matti

  reply	other threads:[~2025-04-09  5:43 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-08  8:40 [PATCH v3 00/14] Support ROHM Scalable PMIC family Matti Vaittinen
2025-04-08  8:40 ` [PATCH v3 01/14] dt-bindings: regulator: Add ROHM BD96802 PMIC Matti Vaittinen
2025-04-08 16:16   ` Conor Dooley
2025-04-09  4:30     ` Matti Vaittinen
2025-04-09  5:43       ` Matti Vaittinen [this message]
2025-04-08  8:40 ` [PATCH v3 02/14] dt-bindings: mfd: " Matti Vaittinen
2025-04-08 16:11   ` Conor Dooley
2025-04-08  8:41 ` [PATCH v3 03/14] dt-bindings: mfd: bd96801: Add ROHM BD96805 Matti Vaittinen
2025-04-08  8:44 ` [PATCH v3 04/14] dt-bindings: mfd: bd96802: Add ROHM BD96806 Matti Vaittinen
2025-04-08 16:09   ` Conor Dooley
2025-04-08  8:44 ` [PATCH v3 05/14] mfd: rohm-bd96801: Add chip info Matti Vaittinen
2025-04-08  8:45 ` [PATCH v3 06/14] mfd: bd96801: Drop IC name from the regulator IRQ resources Matti Vaittinen
2025-04-08  8:45 ` [PATCH v3 07/14] regulator: bd96801: Drop IC name from the " Matti Vaittinen
2025-04-08 20:19   ` Mark Brown
2025-04-08  8:45 ` [PATCH v3 08/14] mfd: rohm-bd96801: Support ROHM BD96802 Matti Vaittinen
2025-04-08  8:46 ` [PATCH v3 09/14] regulator: bd96801: " Matti Vaittinen
2025-04-08 20:19   ` Mark Brown
2025-04-08  8:46 ` [PATCH v3 10/14] mfd: bd96801: Support ROHM BD96805 Matti Vaittinen
2025-04-08  8:46 ` [PATCH v3 11/14] regulator: bd96801: Support ROHM BD96805 PMIC Matti Vaittinen
2025-04-08  8:47 ` [PATCH v3 12/14] mfd: bd96801: Support ROHM BD96806 Matti Vaittinen
2025-04-08  8:47 ` [PATCH v3 13/14] regulator: bd96801: Support ROHM BD96806 PMIC Matti Vaittinen
2025-04-08  8:47 ` [PATCH v3 14/14] MAINTAINERS: Add BD96802 specific header Matti Vaittinen
2025-04-10  7:58 ` [PATCH v3 00/14] Support ROHM Scalable PMIC family Lee Jones
2025-04-10  8:12   ` Matti Vaittinen
2025-04-24 13:58 ` Lee Jones
2025-04-24 13:59   ` Lee Jones
2025-05-02  7:47 ` [GIT PULL] Immutable branch between MFD and Regulator due for the v6.16 merge window Lee Jones
2025-05-02 23:25   ` Mark Brown
2025-05-06  5:28     ` Matti Vaittinen
2025-05-06 14:10       ` Mark Brown
2025-05-06 14:29         ` Matti Vaittinen
2025-05-07 10:33     ` Lee Jones
2025-05-07 10:36       ` Lee Jones

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=62f78786-f9db-4e05-9001-28b786df669b@gmail.com \
    --to=mazziesaccount@gmail.com \
    --cc=broonie@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=conor@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=lee@kernel.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matti.vaittinen@fi.rohmeurope.com \
    --cc=robh@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox