From: "Kambalin, Sergey" <sergey.kambalin@auriga.com>
To: "Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Sergey Kambalin" <serg.oker@gmail.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
"qemu-arm@nongnu.org" <qemu-arm@nongnu.org>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [PATCH] [rpi4b] Make bootable rpi4b model
Date: Mon, 22 May 2023 15:21:03 +0000 [thread overview]
Message-ID: <12ff45b45c334cbd8340becc512eaf89@auriga.com> (raw)
In-Reply-To: <7fb1818b-7ed9-975a-3fa0-ebda7553aa73@linaro.org>
[-- Attachment #1: Type: text/plain, Size: 1490 bytes --]
Thanks for the example, Phillipe! It's helpful!
________________________________
От: Philippe Mathieu-Daudé <philmd@linaro.org>
Отправлено: 22 мая 2023 г. 16:41:53
Кому: Sergey Kambalin; Kambalin, Sergey
Копия: Peter Maydell; qemu-arm@nongnu.org; qemu-devel@nongnu.org
Тема: Re: [PATCH] [rpi4b] Make bootable rpi4b model
On 22/5/23 14:41, Kambalin, Sergey wrote:
>> Could you please tell me what size is appropriate for a single patch?
>
> The most important things for patch splitting are:
> * everything still has to compile cleanly
> * the contents of a single patch should be a coherent single
> thing that it makes sense to review in one part
>
> If there's something in there that only touches 20 lines of
> code but is a coherent single change, it's fine to have that in
> its own patch -- small patches are easy to review.
>
> At the upper end, I tend to think a patch is a bit big
> at around 200 lines, but for the specific case of "here
> is a new device" bigger than that is OK, because it's
> just adding new files rather than merging changes into
> existing ones.
>
> https://www.qemu.org/docs/master/devel/submitting-a-patch.html
> <https://www.qemu.org/docs/master/devel/submitting-a-patch.html>
> has some other advice on patch submission, if you haven't
> read that yet.
FWIW example of series adding the Pi Zero:
https://lore.kernel.org/qemu-devel/20201024170127.3592182-1-f4bug@amsat.org/
[-- Attachment #2: Type: text/html, Size: 2907 bytes --]
prev parent reply other threads:[~2023-05-22 15:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-22 10:29 [PATCH] [rpi4b] Make bootable rpi4b model Sergey Kambalin
2023-05-22 10:32 ` Peter Maydell
2023-05-22 10:42 ` Kambalin, Sergey
2023-05-22 10:58 ` Peter Maydell
2023-05-22 11:42 ` Kambalin, Sergey
2023-05-22 12:01 ` Peter Maydell
2023-05-22 12:41 ` Kambalin, Sergey
2023-05-22 13:41 ` Philippe Mathieu-Daudé
2023-05-22 15:21 ` Kambalin, Sergey [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=12ff45b45c334cbd8340becc512eaf89@auriga.com \
--to=sergey.kambalin@auriga.com \
--cc=peter.maydell@linaro.org \
--cc=philmd@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=serg.oker@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.