From: Daniel Henrique Barboza <danielhb413@gmail.com>
To: Thomas Huth <thuth@redhat.com>, Bin Meng <bmeng.cn@gmail.com>
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
"open list:RISC-V" <qemu-riscv@nongnu.org>,
"qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>,
"Greg Kurz" <groug@kaod.org>, qemu-ppc <qemu-ppc@nongnu.org>,
"Cédric Le Goater" <clg@kaod.org>,
"Guo Zhi" <qtxuning1999@sjtu.edu.cn>,
"David Gibson" <david@gibson.dropbear.id.au>
Subject: Re: [PATCH v1] hw/ppc: change indentation to spaces from TABs
Date: Mon, 11 Apr 2022 13:32:23 -0300 [thread overview]
Message-ID: <453a6303-8519-a2ec-8fd6-e18180f2ad85@gmail.com> (raw)
In-Reply-To: <3e4731dd-c066-71cb-fd4c-6cd2c205bbd7@redhat.com>
On 4/11/22 04:23, Thomas Huth wrote:
> On 11/04/2022 08.57, Bin Meng wrote:
>> On Mon, Apr 11, 2022 at 2:45 PM Thomas Huth <thuth@redhat.com> wrote:
>>>
>>> On 08/04/2022 21.19, Daniel Henrique Barboza wrote:
>>>>
>>>>
>>>> On 4/6/22 07:08, Bin Meng wrote:
>>>>> On Tue, Apr 5, 2022 at 10:36 PM Guo Zhi <qtxuning1999@sjtu.edu.cn> wrote:
>>>>>>
>>>>>> There are still some files in the QEMU PPC code base that use TABs for
>>>>>> indentation instead of using spaces.
>>>>>> The TABs should be replaced so that we have a consistent coding style.
>>>>>>
>>>>>> If this patch is applied, issue:
>>>>>>
>>>>>> https://gitlab.com/qemu-project/qemu/-/issues/374
>>>>>>
>>>>>> can be closed.
>>>>
>>>> Please add the following tag in the commit:
>>>>
>>>>
>>>> Resolves: https://gitlab.com/qemu-project/qemu/-/issues/374
>>>>
>>>>
>>>> This will make Gitlab automatically close the issue when the patch is accepted.
>>>>
>>>>>>
>>>>>> Signed-off-by: Guo Zhi <qtxuning1999@sjtu.edu.cn>
>>>>>> ---
>>>>>> hw/core/uboot_image.h | 185 ++++++++++++++++++++---------------------
>>>>>> hw/ppc/ppc440_bamboo.c | 6 +-
>>>>>> hw/ppc/spapr_rtas.c | 18 ++--
>>>>>> include/hw/ppc/ppc.h | 10 +--
>>>>>> 4 files changed, 109 insertions(+), 110 deletions(-)
>>>>>>
>>>>>> diff --git a/hw/core/uboot_image.h b/hw/core/uboot_image.h
>>>>>
>>>>> uboot_image.h was taken from the U-Boot source, I believe it should be
>>>>> kept as it is.
>>>>
>>>>
>>>> (CCing Thomas since het explictly listed hw/core/uboot_image.h in the bug)
>>>>
>>>>
>>>> I am not sure about keeping this file as is.
>>>
>>> Seems like uboot_image.h has originally been taken from U-Boot's
>>> include/image.h file ... but the two files are completely out of sync
>>> nowadays, e.g. U-Boot switched to enums instead of #defines at one point in
>>> time. So I think it does not make much sense to keep the TABs in here, and
>>> I'd rather like to see them replaced with spaces indeed.
>>
>> This file has been sync'ed recently.
>>
>> See http://patchwork.ozlabs.org/project/qemu-devel/patch/20220324134812.541274-1-bmeng.cn@gmail.com/
>
> Oh, ok, thanks, good to know. So we should maybe really rather drop the uboot_image.h from the whitespace cleanup here, indeed (and rather add a comment to the header file instead that this is a file that is sync'ed with U-Boot and thus does not follow the QEMU coding conventions?)
Agree. I just updated the gitlab issue description to remove the reference to
this file.
Guo Zhi, can you please send another version of this patch with the updated
commit message and not touching uboot_image.h?
Thanks,
Daniel
>
> Anyway, seems like that u-boot sync patch felt through the cracks, likely since it was not quite clear which tree it should go through ... ARM? PPC? RISC-V?
>
> Thomas
>
next prev parent reply other threads:[~2022-04-11 16:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-05 12:19 [PATCH v1] hw/ppc: change indentation to spaces from TABs Guo Zhi
2022-04-06 10:08 ` Bin Meng
2022-04-08 19:19 ` Daniel Henrique Barboza
2022-04-11 6:45 ` Thomas Huth
2022-04-11 6:57 ` Bin Meng
2022-04-11 7:23 ` Thomas Huth
2022-04-11 16:32 ` Daniel Henrique Barboza [this message]
2022-04-11 16:37 ` Guo Zhi
2022-04-12 2:12 ` [PATCH v2] " Guo Zhi
2022-04-13 13:00 ` Daniel Henrique Barboza
2022-04-13 15:03 ` Guo Zhi
2022-04-20 19:18 ` Daniel Henrique Barboza
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=453a6303-8519-a2ec-8fd6-e18180f2ad85@gmail.com \
--to=danielhb413@gmail.com \
--cc=bmeng.cn@gmail.com \
--cc=clg@kaod.org \
--cc=david@gibson.dropbear.id.au \
--cc=groug@kaod.org \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=qemu-riscv@nongnu.org \
--cc=qtxuning1999@sjtu.edu.cn \
--cc=thuth@redhat.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;
as well as URLs for NNTP newsgroup(s).