mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Jeffery <andrew@codeconstruct.com.au>
To: PeterYin <peteryin.openbmc@gmail.com>,
	Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.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
Subject: Re: [PATCH v2 0/6] Revise Meta(Facebook) Harma BMC(AST2600)
Date: Fri, 22 Nov 2024 11:27:08 +1030	[thread overview]
Message-ID: <920e053a17d5f9a7d5805bcd674f036a9c7fb402.camel@codeconstruct.com.au> (raw)
In-Reply-To: <b13e5063-3b07-43ec-a7cc-b19e73b7c9e0@gmail.com>

Hi Peter,

On Thu, 2024-11-21 at 12:33 +0800, PeterYin wrote:
> Hi Andrew,
>    I believe this series' path will conflict with upstream due to 
> version differences between OpenBMC and upstream. I will update to
> the 
> latest version of the DTS from upstream and submit a new version 
> accordingly.

Going forward, please make sure that patches you send upstream have
been tested on upstream (in terms of whether they apply to the
appropriate branch, and whether they have the right effect on the
system at runtime).

Andrew

  reply	other threads:[~2024-11-22  0:57 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-21  2:53 Peter Yin
2024-11-21  2:53 ` [PATCH v2 1/6] ARM: dts: aspeed: Harma: Revise node name Peter Yin
2024-11-21  2:53 ` [PATCH v2 2/6] ARM: dts: aspeed: Harma: Add retimer device Peter Yin
2024-11-21  2:53 ` [PATCH v2 3/6] ARM: dts: aspeed: Harma: Revise GPIO line name Peter Yin
2024-11-21  2:53 ` [PATCH v2 4/6] ARM: dts: aspeed: Harma: add e1s power monitor Peter Yin
2024-11-21  2:53 ` [PATCH v2 5/6] ARM: dts: aspeed: Harma: fan board io-expander Peter Yin
2024-11-21  2:53 ` [PATCH v2 6/6] ARM: dts: aspeed: Harma: add adc128d818 Peter Yin
2024-11-21  4:33 ` [PATCH v2 0/6] Revise Meta(Facebook) Harma BMC(AST2600) PeterYin
2024-11-22  0:57   ` Andrew Jeffery [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-01-04 13:45 Peter Yin
2024-01-04 14:28 ` Patrick Williams

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=920e053a17d5f9a7d5805bcd674f036a9c7fb402.camel@codeconstruct.com.au \
    --to=andrew@codeconstruct.com.au \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=joel@jms.id.au \
    --cc=krzysztof.kozlowski+dt@linaro.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+dt@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®