mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Jeffery <andrew@codeconstruct.com.au>
To: Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	 Conor Dooley <conor+dt@kernel.org>,
	Joel Stanley <joel@jms.id.au>,
	 devicetree@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	 linux-aspeed@lists.ozlabs.org, linux-kernel@vger.kernel.org,
	 Fred Chen <fredchen.openbmc@gmail.com>
Subject: Re: [PATCH v2 0/2] Add Meta (Facebook) Santabarbara BMC (AST2600)
Date: Fri, 27 Jun 2025 10:29:37 +0930	[thread overview]
Message-ID: <175098597713.150233.11475739280254945170.b4-ty@codeconstruct.com.au> (raw)
In-Reply-To: <20250625073847.4054971-1-fredchen.openbmc@gmail.com>

On Wed, 25 Jun 2025 15:38:36 +0800, Fred Chen wrote:
> Summary:
> Add linux device tree entry related to Meta (Facebook) Santabarbara
> specific devices connected to BMC (AST2600) SoC.
> 
> Change log
> v1 -> v2:
>   - Enable mac3 node
>   - Add GPIO line-name FM_MUX1_SEL_R
>   - Remove 'pinctrl-names' from gpio0 node
>   - Reorder top-level nodes alphabetically
>   - Reorder device node properties per style
> v1:
>   - Create santabarbara dts file.
> 
> [...]

Thanks, I've applied this to be picked up through the BMC tree.

-- 
Andrew Jeffery <andrew@codeconstruct.com.au>


      parent reply	other threads:[~2025-06-27  0:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-25  7:38 Fred Chen
2025-06-25  7:38 ` [PATCH v2 1/2] dt-bindings: arm: aspeed: add Meta Santabarbara board Fred Chen
2025-06-27 20:38   ` Rob Herring (Arm)
2025-06-25  7:38 ` [PATCH v2 2/2] ARM: dts: aspeed: santabarbara: Add Meta Santabarbara BMC Fred Chen
2025-06-25 20:25 ` [PATCH v2 0/2] Add Meta (Facebook) Santabarbara BMC (AST2600) Rob Herring (Arm)
2025-06-27  0:59 ` Andrew Jeffery [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=175098597713.150233.11475739280254945170.b4-ty@codeconstruct.com.au \
    --to=andrew@codeconstruct.com.au \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=fredchen.openbmc@gmail.com \
    --cc=joel@jms.id.au \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-aspeed@lists.ozlabs.org \
    --cc=linux-kernel@vger.kernel.org \
    --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
all inboxes | Powered by JetHome®