From: "Jiaxun Yang" <jiaxun.yang@flygoat.com>
To: "Philippe Mathieu-Daudé" <f4bug@amsat.org>,
"BALATON Zoltan via" <qemu-devel@nongnu.org>
Cc: Aleksandar Rikalo <aleksandar.rikalo@syrmia.com>,
"paulburton@kernel.org" <paulburton@kernel.org>
Subject: Re: [PATCH v3 0/3] hw/mips/boston: ELF kernel support
Date: Fri, 15 Oct 2021 22:46:57 +0100 [thread overview]
Message-ID: <799b81fe-17b9-416d-b320-dd9f9e8c610f@www.fastmail.com> (raw)
In-Reply-To: <f840d219-5562-f4af-8eeb-7c7df87f4741@amsat.org>
在2021年10月15日十月 上午9:49，Philippe Mathieu-Daudé写道：
> On 10/11/21 15:58, Jiaxun Yang wrote:
>> ping?
>>
>> 在 2021/10/2 19:45, Jiaxun Yang 写道:
>>> Jiaxun Yang (3):
>>> hw/mips/boston: Massage memory map information
>>> hw/mips/boston: Allow loading elf kernel and dtb
>>> hw/mips/boston: Add FDT generator
>
> Next time please run checkpatch.pl before submitting,
> see
> https://blog.vmsplice.net/2011/03/how-to-automatically-run-checkpatchpl.html
>
Thanks!
I have ran checkpatch.pl before sending but was taught to ignore over length warning by kernel community :-(
Apparently QEMU is not the case.
--
- Jiaxun
prev parent reply other threads:[~2021-10-15 21:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-02 18:45 [PATCH v3 0/3] hw/mips/boston: ELF kernel support Jiaxun Yang
2021-10-02 18:45 ` [PATCH v3 1/3] hw/mips/boston: Massage memory map information Jiaxun Yang
2021-10-02 18:45 ` [PATCH v3 2/3] hw/mips/boston: Allow loading elf kernel and dtb Jiaxun Yang
2021-10-02 18:45 ` [PATCH v3 3/3] hw/mips/boston: Add FDT generator Jiaxun Yang
2021-10-03 17:45 ` Philippe Mathieu-Daudé
2021-10-03 20:20 ` Jiaxun Yang
2021-10-11 13:58 ` [PATCH v3 0/3] hw/mips/boston: ELF kernel support Jiaxun Yang
2021-10-15 8:49 ` Philippe Mathieu-Daudé
2021-10-15 21:46 ` Jiaxun Yang [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=799b81fe-17b9-416d-b320-dd9f9e8c610f@www.fastmail.com \
--to=jiaxun.yang@flygoat.com \
--cc=aleksandar.rikalo@syrmia.com \
--cc=f4bug@amsat.org \
--cc=paulburton@kernel.org \
--cc=qemu-devel@nongnu.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).