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
