From: Marc Zyngier <marc.zyngier@arm.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: "Stephen Rothwell" <sfr@canb.auug.org.au>,
"Christoffer Dall" <cdall@cs.columbia.edu>,
"Catalin Marinas" <catalin.marinas@arm.com>,
"Will Deacon" <will.deacon@arm.com>,
"Linux-Next Mailing List" <linux-next@vger.kernel.org>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Suzuki K Poulose" <suzuki.poulose@arm.com>,
"Radim Krčmář" <rkrcmar@redhat.com>, KVM <kvm@vger.kernel.org>
Subject: Re: linux-next: manual merge of the kvm-arm tree with the arm64 tree
Date: Fri, 17 Aug 2018 10:33:42 +0100 [thread overview]
Message-ID: <86d0uhpcax.wl-marc.zyngier@arm.com> (raw)
In-Reply-To: <84803922-9430-43d2-7db6-e9c0dd02da6a@redhat.com>
On Fri, 17 Aug 2018 09:32:55 +0100,
Paolo Bonzini <pbonzini@redhat.com> wrote:
>
> On 16/08/2018 02:15, Stephen Rothwell wrote:
> >> -#define ARM64_HAS_STAGE2_FWB 31
> >> +#define ARM64_MISMATCHED_CACHE_TYPE 31
> >> ++#define ARM64_HAS_STAGE2_FWB 32
> >>
> >> --#define ARM64_NCAPS 32
> >> ++#define ARM64_NCAPS 33
> >>
> >> #endif /* __ASM_CPUCAPS_H */
> > This is now a conflict between Linus' tree and the kvm-arm tree (and
> > presumably soon the kvm tree).
>
> This should have been sorted out using topic branches. I'll handle it
> myself by splitting the pull request in two, but please try to organize
> better the changes in non-KVM-specific arch/arm and arch/arm64 files.
We've dealt with that kind of trivial conflicts in the past without
requiring topic branches (cpucaps.h has always been a popular place),
and I always assumed that this was acceptable. I must have
misunderstood something here.
Next time, I'll direct the architecture-specific code via the arm64
tree directly.
Thanks,
M.
--
Jazz is not dead, it just smell funny.
next prev parent reply other threads:[~2018-08-17 9:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180723144641.62b2b226@canb.auug.org.au>
2018-08-16 0:15 ` linux-next: manual merge of the kvm-arm tree with the arm64 tree Stephen Rothwell
2018-08-17 8:32 ` Paolo Bonzini
2018-08-17 9:33 ` Marc Zyngier [this message]
[not found] <20250317171701.71c8677a@canb.auug.org.au>
2025-03-21 4:29 ` Stephen Rothwell
[not found] <20241031143519.73eca58b@canb.auug.org.au>
2024-11-15 4:05 ` Stephen Rothwell
[not found] <20231017123017.3907baac@canb.auug.org.au>
2023-11-01 2:36 ` Stephen Rothwell
[not found] <20230615122201.75e36abd@canb.auug.org.au>
2023-07-03 0:50 ` Stephen Rothwell
[not found] <20220504143529.4060ab27@canb.auug.org.au>
2022-05-23 6:36 ` Stephen Rothwell
[not found] <20180328160541.5b900f71@canb.auug.org.au>
2018-03-29 5:16 ` Stephen Rothwell
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=86d0uhpcax.wl-marc.zyngier@arm.com \
--to=marc.zyngier@arm.com \
--cc=catalin.marinas@arm.com \
--cc=cdall@cs.columbia.edu \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=rkrcmar@redhat.com \
--cc=sfr@canb.auug.org.au \
--cc=suzuki.poulose@arm.com \
--cc=will.deacon@arm.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