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,
	 Peter Yin <peteryin.openbmc@gmail.com>
Subject: Re: [PATCH v2 0/5] Revise Meta(Facebook) Harma BMC(AST2600)
Date: Fri, 13 Jun 2025 14:49:51 +0930	[thread overview]
Message-ID: <174979199120.342730.12220286428468673903.b4-ty@codeconstruct.com.au> (raw)
In-Reply-To: <20250611080514.3123335-1-peteryin.openbmc@gmail.com>

On Wed, 11 Jun 2025 16:05:09 +0800, Peter Yin wrote:
> Summary:
> Revise linux device tree entry related to Meta(Facebook) Harma
> specific devices connected to BMC(AST2600) SoC.
> 
> Based on:
> https://github.com/torvalds/linux/blob/master/arch/arm/boot/dts/aspeed/aspeed-bmc-facebook-harma.dts
> commit-id: cb3f397b17bbda3f2998eff9e54b040c8fa85cc9
> 
> [...]

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-13  5:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-11  8:05 Peter Yin
2025-06-11  8:05 ` [PATCH v2 1/5] ARM: dts: aspeed: harma: add E1.S power monitor Peter Yin
2025-06-11  8:05 ` [PATCH v2 2/5] ARM: dts: aspeed: harma: add fan board I/O expander Peter Yin
2025-06-11  8:05 ` [PATCH v2 3/5] ARM: dts: aspeed: harma: add ADC128D818 for voltage monitoring Peter Yin
2025-06-11  8:05 ` [PATCH v2 4/5] ARM: dts: aspeed: Harma: revise gpio bride pin for battery Peter Yin
2025-06-11  8:05 ` [PATCH v2 5/5] ARM: dts: aspeed: harma: add mmc health Peter Yin
2025-06-13  5:19 ` 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=174979199120.342730.12220286428468673903.b4-ty@codeconstruct.com.au \
    --to=andrew@codeconstruct.com.au \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --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=peteryin.openbmc@gmail.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

all inboxes | Powered by JetHome®