Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.31 as permitted sender) client-ip=23.128.96.31;
Message-ID: <f94e3405-20c5-4701-8217-9542affef46f@linux.microsoft.com>
Date:   Wed, 11 Oct 2023 18:56:04 -0700
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: [PATCH v2 13/15] uapi: hyperv: Add mshv driver headers hvhdk.h,
 hvhdk_mini.h, hvgdk.h, hvgdk_mini.h
Content-Language: en-US
To:     Greg KH <gregkh@linuxfoundation.org>
Cc:     Wei Liu <wei.liu@kernel.org>, linux-hyperv@vger.kernel.org,
        linux-kernel@vger.kernel.org, x86@kernel.org,
        linux-arm-kernel@lists.infradead.org, linux-arch@vger.kernel.org,
        patches@lists.linux.dev, mikelley@microsoft.com, kys@microsoft.com,
        haiyangz@microsoft.com, decui@microsoft.com,
        apais@linux.microsoft.com, Tianyu.Lan@microsoft.com,
        ssengar@linux.microsoft.com, mukeshrathor@microsoft.com,
        stanislav.kinsburskiy@gmail.com, jinankjain@linux.microsoft.com,
        vkuznets@redhat.com, tglx@linutronix.de, mingo@redhat.com,
        bp@alien8.de, dave.hansen@linux.intel.com, hpa@zytor.com,
        will@kernel.org, catalin.marinas@arm.com
References: <1692309711-5573-1-git-send-email-nunodasneves@linux.microsoft.com>
 <1692309711-5573-14-git-send-email-nunodasneves@linux.microsoft.com>
 <ZN6m2gVmtVStuEfA@liuwe-devbox-debian-v2> <2023081923-crown-cake-79f7@gregkh>
 <c4482a6a-aed0-4750-aa1b-421f0e541cfa@linux.microsoft.com>
 <50f1721f-64fb-49ff-9740-0dac7cf832c8@linux.microsoft.com>
 <2023101133-blade-diary-11e4@gregkh>
From:   Nuno Das Neves <nunodasneves@linux.microsoft.com>
In-Reply-To: <2023101133-blade-diary-11e4@gregkh>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Precedence: bulk

On 10/10/2023 11:42 PM, Greg KH wrote:
> On Tue, Oct 10, 2023 at 03:49:48PM -0700, Nuno Das Neves wrote:
>> On 8/25/2023 11:24 AM, Nuno Das Neves wrote:
>>> On 8/19/2023 3:26 AM, Greg KH wrote:
>>>>
>>>> My "strong" opinion is the one kernel development rule that we have,
>>>> "you can not break userspace".  So, if you change these
>>>> values/structures/whatever in the future, and userspace tools break,
>>>> that's not ok and the changes have to be reverted.
>>>>
>>>> If you can control both sides of the API here (with open tools that you
>>>> can guarantee everyone will always update to), then yes, you can change
>>>> the api in the future.
>>>>

We control both sides of the API. The code is open. No one else can use it
today, therefore we can guarantee all the users will stay updated.

> Just submit your fixed up patch series based on the previous review
> comments and it will be reviewed again, just like all kernel patches
> are.

I will do that.

> Perhaps you all should take the time to do some kernel patch reviews of
> other stuff sent to the mailing lists to get an idea of how this whole
> process works, and to get better integrated into the kernel development
> community,

That is a good suggestion, I will do that.

> before dumping a huge patchset on us with lots of process
> questions like this?  Why are you asking the community to do a lot of
> work and hand-holding when you aren't helping others out as well?

I take your point, sorry my questions came off that way. I will work to
improve on that :)

Thanks,
Nuno