From: Krzysztof Kozlowski <krzk@kernel.org>
To: Eddie James <eajames@linux.ibm.com>, linux-aspeed@lists.ozlabs.org
Cc: devicetree@vger.kernel.org, andrew@codeconstruct.com.au,
joel@jms.id.au, conor+dt@kernel.org, krzk+dt@kernel.org,
robh@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 0/4] ARM: dts: aspeed: Add IBM P11 BMC systems
Date: Wed, 15 May 2024 16:10:32 +0200 [thread overview]
Message-ID: <b99b61bd-a271-4dc8-b8fc-ab72df65dc1b@kernel.org> (raw)
In-Reply-To: <20240514213510.159144-1-eajames@linux.ibm.com>
On 14/05/2024 23:35, Eddie James wrote:
> This series was previously included in
> https://lore.kernel.org/all/20240429210131.373487-1-eajames@linux.ibm.com/
> The series now depends on
> https://lore.kernel.org/all/20240514212555.158788-1-eajames@linux.ibm.com/
No, it does not work like this. Bindings come with the user. Do not
create fake dependencies and DTS must be send TOGETHER with the board
binding.
Best regards,
Krzysztof
prev parent reply other threads:[~2024-05-15 14:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-14 21:35 [PATCH v5 0/4] ARM: dts: aspeed: Add IBM P11 BMC systems Eddie James
2024-05-14 21:35 ` [PATCH v5 1/4] ARM: dts: aspeed: Add IBM P11 FSI devices Eddie James
2024-05-14 21:35 ` [PATCH v5 2/4] ARM: dts: aspeed: Add IBM P11 Blueridge BMC system Eddie James
2024-05-15 14:11 ` Krzysztof Kozlowski
2024-05-14 21:35 ` [PATCH v5 3/4] ARM: dts: aspeed: Add IBM P11 Blueridge 4U " Eddie James
2024-05-14 21:35 ` [PATCH v5 4/4] ARM: dts: aspeed: Add IBM P11 Fuji " Eddie James
2024-05-15 13:13 ` [PATCH v5 0/4] ARM: dts: aspeed: Add IBM P11 BMC systems Rob Herring (Arm)
2024-05-15 14:10 ` Krzysztof Kozlowski [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=b99b61bd-a271-4dc8-b8fc-ab72df65dc1b@kernel.org \
--to=krzk@kernel.org \
--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-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).