From: Quan Nguyen <quan@os.amperecomputing.com>
To: Arnd Bergmann <arnd@arndb.de>, Joel Stanley <joel@jms.id.au>
Cc: openbmc@lists.ozlabs.org, Olof Johansson <olof@lixom.net>,
soc@kernel.org, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Andrew Jeffery <andrew@aj.id.au>,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-aspeed@lists.ozlabs.org,
Open Source Submission <patches@amperecomputing.com>,
Phong Vo <phong@os.amperecomputing.com>,
thang@os.amperecomputing.com
Subject: Re: [PATCH v3 2/2] ARM: dts: aspeed: Add device tree for Ampere's Mt. Mitchell BMC
Date: Wed, 21 Sep 2022 14:57:27 +0700 [thread overview]
Message-ID: <60188017-8f96-0773-7eaf-43d877f876b2@os.amperecomputing.com> (raw)
In-Reply-To: <b34ab4d0-c14f-caeb-afde-01655b35a236@os.amperecomputing.com>
Hi Arnd,
I'm really sorry but I have to ping you again as I'm confused and still
wonder if anything else could be updated to this patchset. Could you
share some suggestion on what to do next ? or should I resend it?
The only thing left is Joel's complaint about there is no output to test
with bootargs removed. I have tried and see it could be fixed by using
the -append option with qemu.
Besides, Joel also says it "looks ready to merge" and give a Reviewed-by
already.
Thank you and best regards,
- Quan
On 13/09/2022 14:42, Quan Nguyen wrote:
> Hi,
>
> Just a gentle ping on the patch.
>
> Thanks and best regards,
> - Quan
>
> On 05/09/2022 16:45, Quan Nguyen wrote:
>>
>>
>> On 25/08/2022 19:35, Arnd Bergmann wrote:
>>> On Tue, Aug 23, 2022 at 10:27 AM Quan Nguyen
>>> <quan@os.amperecomputing.com> wrote:
>>>> On 18/08/2022 19:06, Arnd Bergmann wrote:
>>>>
>>>> Thanks Arnd for the comment.
>>>>
>>>> I think adding -append could solve the issue.
>>>>
>>>> But as the bootargs still exist in all other
>>>> arch/arm/boot/dts/aspeed-bmc-*.dts should we still keep bootargs for
>>>> this dts?
>>>
>>> I think it should still be removed. Only 238 of 2547 set the console
>>> using
>>> bootargs, so that would make it more consistent with the other files.
>>>
>>> Changing the files that have the same issue is a separate matter.
>>>
>>
>> Hi Joel,
>>
>> In the meantime, I'm just wonder if you could help to test the patch
>> with -append and get it merged.
>>
>> Thank you and best regards,
>> - Quan
prev parent reply other threads:[~2022-09-21 7:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-17 7:15 [PATCH v3 0/2] " Quan Nguyen
2022-08-17 7:15 ` [PATCH v3 1/2] dt-bindings: arm: aspeed: document Ampere Mt.Mitchell BMC compatibles Quan Nguyen
2022-08-17 7:46 ` Krzysztof Kozlowski
2022-08-17 7:15 ` [PATCH v3 2/2] ARM: dts: aspeed: Add device tree for Ampere's Mt. Mitchell BMC Quan Nguyen
2022-08-18 7:33 ` Joel Stanley
2022-08-18 12:06 ` Arnd Bergmann
2022-08-23 8:27 ` Quan Nguyen
2022-08-25 12:35 ` Arnd Bergmann
2022-09-05 9:45 ` Quan Nguyen
2022-09-13 7:42 ` Quan Nguyen
2022-09-21 7:57 ` Quan Nguyen [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=60188017-8f96-0773-7eaf-43d877f876b2@os.amperecomputing.com \
--to=quan@os.amperecomputing.com \
--cc=andrew@aj.id.au \
--cc=arnd@arndb.de \
--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=olof@lixom.net \
--cc=openbmc@lists.ozlabs.org \
--cc=patches@amperecomputing.com \
--cc=phong@os.amperecomputing.com \
--cc=robh+dt@kernel.org \
--cc=soc@kernel.org \
--cc=thang@os.amperecomputing.com \
/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®