From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Andrew Jeffery <andrew@codeconstruct.com.au>,
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 1/4] ARM: dts: aspeed: greatlakes: correct Mellanox multi-host property
Date: Fri, 5 Apr 2024 08:48:12 +0200 [thread overview]
Message-ID: <a4276893-ba74-4baf-bcb9-9aee9f90d8c0@linaro.org> (raw)
In-Reply-To: <65060691d4649c4a8da46e5ba762a3c905ade690.camel@codeconstruct.com.au>
On 05/04/2024 01:21, Andrew Jeffery wrote:
>>>
>>> Acked-by: Andrew Jeffery <andrew@codeconstruct.com.au>
>>>
>>> I'm working to stay on top of things a bit more now than I have in the
>>> recent past, so hopefully I won't miss patches again in the future.
>>
>> Stephen reported conflict, although trivial, but maybe better if you
>> take them?
>>
>
> Yeah, happy to.
>
>> I can rebase and resend.
I dropped these patches (and one more) from my tree, rebased and resent
everything as v2.
Thanks!
Best regards,
Krzysztof
prev parent reply other threads:[~2024-04-05 6:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-09 10:44 Krzysztof Kozlowski
2023-12-09 10:44 ` [PATCH 2/4] ARM: dts: aspeed: minerva-cmc: " Krzysztof Kozlowski
2023-12-09 10:44 ` [PATCH 3/4] ARM: dts: aspeed: yosemite4: " Krzysztof Kozlowski
2023-12-09 10:44 ` [PATCH 4/4] ARM: dts: aspeed: yosemitev2: " Krzysztof Kozlowski
2024-04-03 10:04 ` [PATCH 1/4] ARM: dts: aspeed: greatlakes: " Krzysztof Kozlowski
2024-04-04 1:41 ` Andrew Jeffery
2024-04-04 6:13 ` Krzysztof Kozlowski
2024-04-04 23:21 ` Andrew Jeffery
2024-04-05 6:48 ` 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=a4276893-ba74-4baf-bcb9-9aee9f90d8c0@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=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=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®