public inbox for linux-arm-kernel@lists.infradead.org 
 help / color / mirror / Atom feed
From: Dawid Glazik <dawid.glazik@linux•intel.com>
To: Andrew Jeffery <andrew@codeconstruct•com.au>,
	Lee Jones <lee@kernel•org>, Rob Herring <robh@kernel•org>,
	Krzysztof Kozlowski <krzk+dt@kernel•org>,
	Conor Dooley <conor+dt@kernel•org>, Joel Stanley <joel@jms•id.au>,
	linux-aspeed@lists•ozlabs.org
Cc: devicetree@vger•kernel.org, linux-arm-kernel@lists•infradead.org,
	linux-kernel@vger•kernel.org, maciej.lawniczak@intel•com
Subject: Re: [PATCH v4 0/3] ARM: dts: aspeed-g6: add AST2600 I3C nodes and bindings
Date: Tue, 19 May 2026 10:19:45 +0200	[thread overview]
Message-ID: <62d6af80-62f1-4b74-b4e7-3311d319f56b@linux.intel.com> (raw)
In-Reply-To: <23203c124a158536c272d1bffb2657a0d713f8ce.camel@codeconstruct.com.au>

On 5/18/2026 7:02 AM, Andrew Jeffery wrote:
> 
> Sorry for the delay.
> 
> Given Krzysztof's R-b tag for patch 2 I've applied 3 (along with 1) to
> the BMC tree. Patch 2 should be picked up by Lee through the MFD tree.
> 
> Cheers,
> 
> Andrew

Hi Andrew,

Great news! Thank you.

Dawid


      reply	other threads:[~2026-05-19  8:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-24 20:20 [PATCH v4 0/3] ARM: dts: aspeed-g6: add AST2600 I3C nodes and bindings Dawid Glazik
2026-04-24 20:20 ` [PATCH v4 1/3] ARM: dts: aspeed-g6: move i2c controllers directly into apb node Dawid Glazik
2026-04-24 20:21 ` [PATCH v4 2/3] dt-bindings: mfd: syscon: add aspeed,ast2600-i3c-global compatible Dawid Glazik
2026-04-25  9:40   ` Krzysztof Kozlowski
2026-06-05  0:43     ` Andrew Jeffery
2026-04-24 20:21 ` [PATCH v4 3/3] ARM: dts: aspeed-g6: Add nodes for i3c controllers Dawid Glazik
2026-05-11 14:14 ` [PATCH v4 0/3] ARM: dts: aspeed-g6: add AST2600 I3C nodes and bindings Dawid Glazik
2026-05-18  5:02   ` Andrew Jeffery
2026-05-19  8:19     ` Dawid Glazik [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=62d6af80-62f1-4b74-b4e7-3311d319f56b@linux.intel.com \
    --to=dawid.glazik@linux$(echo .)intel.com \
    --cc=andrew@codeconstruct$(echo .)com.au \
    --cc=conor+dt@kernel$(echo .)org \
    --cc=devicetree@vger$(echo .)kernel.org \
    --cc=joel@jms$(echo .)id.au \
    --cc=krzk+dt@kernel$(echo .)org \
    --cc=lee@kernel$(echo .)org \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    --cc=linux-aspeed@lists$(echo .)ozlabs.org \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=maciej.lawniczak@intel$(echo .)com \
    --cc=robh@kernel$(echo .)org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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