[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAK8P3a1yCBO5fJ8pacxVd4Umjt0Qy7wfgwZNkqqYMKjofZFvLQ@mail.gmail.com>
Date: Wed, 11 May 2022 22:02:43 +0200
From: Arnd Bergmann <arnd@...db.de>
To: Vishnu Dasa <vdasa@...are.com>
Cc: Vitaly Kuznetsov <vkuznets@...hat.com>,
Pv-drivers <Pv-drivers@...are.com>,
linux-kernel-review list
<linux-kernel-review@...lman2.vmware.com>,
Cyprien Laplace <claplace@...are.com>,
Bryan Tan <bryantan@...are.com>,
"gregkh@...uxfoundation.org" <gregkh@...uxfoundation.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"virtualization@...ts.linux-foundation.org"
<virtualization@...ts.linux-foundation.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH] VMCI: Add support for ARM64
On Wed, May 11, 2022 at 9:54 PM Vishnu Dasa <vdasa@...are.com> wrote:
>
>
> > FWIW, it seems you're doing three things at once, better split this into
> > a 3-patch series.
>
> Thanks for the feedback. I was debating between the two ways of doing
> it and ultimately did it one way. It is a bit late now to change it as it has
> made its way to linux-next already.
It's really ok either way here. While there are clearly multiple changes in the
source file, they are all trivial, and the Kconfig change doesn't make sense
without the other changes, so having a combined patch seems totally
reasonable as well.
Arnd
Powered by blists - more mailing lists