qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: Shuuichirou Ishii <ishii.shuuichir@fujitsu.com>
Cc: qemu-arm <qemu-arm@nongnu.org>, QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [PATCH v2 0/3] Add support for Fujitsu A64FX processor
Date: Fri, 30 Jul 2021 11:38:31 +0100	[thread overview]
Message-ID: <CAFEAcA_=685EKqdsLh=rnXPXQNSRJ+PNuDYec5LTxr_rcAbeOQ@mail.gmail.com> (raw)
In-Reply-To: <20210730030821.231106-1-ishii.shuuichir@fujitsu.com>

On Fri, 30 Jul 2021 at 04:08, Shuuichirou Ishii
<ishii.shuuichir@fujitsu.com> wrote:
>
> This is the v2 patch series.
>
> v2:
> No features have been added or removed from the v1 patch series. Removal
> of unused definitions that were added in excess, and consolidation of
> patches for the purpose of functional consistency.
>
> For patch 1, ARM_FEATURE_A64FX is not used in the v1 patch series, so it
> was deleted this time, and will be added again when it is used.
>
> For patch 2, since the a64fx_cp_reginfo structure is not used in the v1
> patch series, I deleted the empty definition and added the TODO in the
> aarch64_a64fx_initfn function. Also fixed the appearance, and cleaned up
> and removed some things for patch consistency.
>
> For patch 3, a64fx was added to docs/system/arm/virt.rst and
> hw/arm/virt.c respectively, as a modification to the patch consistency
> cleanup done in patch 2.

I'm afraid this isn't the way a v2 patchseries should be structured.
The idea is that a v2 series should be complete in itself, not based
on whatever v1 was. So when you make the changes requested in review
of v1, you update the commits in your local git branch, and then you
send out the patches as the v2. v2 should apply cleanly on to master,
and all the patches in it should be logically separated out changes
(with no "patch 1 makes a change and then patch 2 changes the code
that was added in patch 1" effects).

thanks
-- PMM


  parent reply	other threads:[~2021-07-30 10:40 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-30  3:08 [PATCH v2 0/3] Add support for Fujitsu A64FX processor Shuuichirou Ishii
2021-07-30  3:08 ` [PATCH v2 1/3] target-arm: delete ARM_FEATURE_A64FX Shuuichirou Ishii
2021-07-30 10:34   ` Peter Maydell
2021-08-03  0:23     ` ishii.shuuichir
2021-07-30 10:36   ` Alex Bennée
2021-08-03  0:32     ` ishii.shuuichir
2021-07-30  3:08 ` [PATCH v2 2/3] target-arm: cpu64: Add support for Fujitsu A64FX Shuuichirou Ishii
2021-07-30  3:08 ` [PATCH v2 3/3] target-arm: Add A64FX processor support to virt machine Shuuichirou Ishii
2021-07-30 10:36   ` Peter Maydell
2021-08-03  0:21     ` ishii.shuuichir
2021-07-30 10:38 ` Peter Maydell [this message]
2021-08-03  0:36   ` [PATCH v2 0/3] Add support for Fujitsu A64FX processor ishii.shuuichir
2021-08-03  9:03     ` Peter Maydell
  -- strict thread matches above, loose matches on Subject: below --
2021-07-30  1:40 Shuuichirou Ishii

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='CAFEAcA_=685EKqdsLh=rnXPXQNSRJ+PNuDYec5LTxr_rcAbeOQ@mail.gmail.com' \
    --to=peter.maydell@linaro.org \
    --cc=ishii.shuuichir@fujitsu.com \
    --cc=qemu-arm@nongnu.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).