Thank you very much for the answers, it has been very useful. El sáb., 5 oct. 2019 a las 11:00, <kernelnewbies-request@kernelnewbies.org> escribió:
Send Kernelnewbies mailing list submissions to kernelnewbies@kernelnewbies.org
To subscribe or unsubscribe via the World Wide Web, visit https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies or, via email, send a message with subject or body 'help' to kernelnewbies-request@kernelnewbies.org
You can reach the person managing the list at kernelnewbies-owner@kernelnewbies.org
When replying, please edit your Subject line so it is more specific than "Re: Contents of Kernelnewbies digest..."
Today's Topics:
1. Re: Remote I/O bus (Valdis Kl=?utf-8?Q?=c4=93?=tnieks) 2. Test the kernel code (CRISTIAN ANDRES VARGAS GONZALEZ) 3. Re: Test the kernel code (Adam Zerella) 4. Re: Test the kernel code (Valdis Kl=?utf-8?Q?=c4=93?=tnieks) 5. suspend mode (nunojsa)
----------------------------------------------------------------------
Message: 1 Date: Fri, 04 Oct 2019 17:51:17 -0400 From: "Valdis Kl=?utf-8?Q?=c4=93?=tnieks" <valdis.kletnieks@vt.edu> To: Luca Ceresoli <luca@lucaceresoli.net> Cc: Greg KH <greg@kroah.com>, kernelnewbies@kernelnewbies.org Subject: Re: Remote I/O bus Message-ID: <154634.1570225877@turing-police> Content-Type: text/plain; charset="us-ascii"
On Fri, 04 Oct 2019 17:08:30 +0200, Luca Ceresoli said:
Yes, the read/write helpers are nicely isolated. However this sits in a vendor kernel that tends to change a lot from one release to another, so
I admit having a hard time wrapping my head around "vendor kernel that changes a lot from one release to another", unless you mean something like the RedHat Enterprise releases that updates every 2 years, and at that point you get hit with a jump of 8 or 10 kernel releases.
And of course, the right answer is to fix up the driver and upstream it, so that in 2022 when your vendor does a new release, the updated driver will already be there waiting for you.
And don't worry about having to do patches to update the driver to a new kernel release because APIs change - that's only a problem for out-of-tree drivers. If it's in-tree, the person making the API change is supposed to fix your driver for you.