From: Ninad Palsule <ninad@linux.ibm.com>
To: Andrew Jeffery <andrew@codeconstruct.com.au>,
robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
joel@jms.id.au, eajames@linux.ibm.com
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-aspeed@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 0/3] Device tree changes for system1 BMC
Date: Tue, 1 Oct 2024 22:12:10 -0500 [thread overview]
Message-ID: <434b4a7c-59ca-47c2-a90f-b4fb994bccac@linux.ibm.com> (raw)
In-Reply-To: <172782880678.751051.14871757116202304815.b4-ty@codeconstruct.com.au>
Hi Andrew,
On 10/1/24 19:26, Andrew Jeffery wrote:
> On Tue, 01 Oct 2024 14:17:47 -0500, Ninad Palsule wrote:
>> Please review the device tree changes for BMC for system1 machine.
>>
>> Ninad Palsule (3):
>> ARM: dts: aspeed: system1: Bump up i2c busses freq
>> ARM: dts: aspeed: system1: Enable serial gpio0
>> ARM: dts: aspeed: system1: Add GPIO line names
>>
>> [...]
> Thanks, I've applied this to be picked up through the BMC tree.
Thank you!
>
> --
> Andrew Jeffery <andrew@codeconstruct.com.au>
>
prev parent reply other threads:[~2024-10-02 3:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-01 19:17 [PATCH v1 0/3] Device tree changes for system1 BMC Ninad Palsule
2024-10-01 19:17 ` [PATCH v1 1/3] ARM: dts: aspeed: system1: Bump up i2c busses freq Ninad Palsule
2024-10-01 20:48 ` Eddie James
2024-10-01 19:17 ` [PATCH v1 2/3] ARM: dts: aspeed: system1: Enable serial gpio0 Ninad Palsule
2024-10-01 20:49 ` Eddie James
2024-10-01 19:17 ` [PATCH v1 3/3] ARM: dts: aspeed: system1: Add GPIO line names Ninad Palsule
2024-10-01 20:50 ` Eddie James
2024-10-02 0:26 ` [PATCH v1 0/3] Device tree changes for system1 BMC Andrew Jeffery
2024-10-02 3:12 ` Ninad Palsule [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=434b4a7c-59ca-47c2-a90f-b4fb994bccac@linux.ibm.com \
--to=ninad@linux.ibm.com \
--cc=andrew@codeconstruct.com.au \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=eajames@linux.ibm.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;
as well as URLs for NNTP newsgroup(s).