From: "Valdis Klē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
Date: Fri, 04 Oct 2019 17:51:17 -0400 [thread overview]
Message-ID: <154634.1570225877@turing-police> (raw)
In-Reply-To: <442abb4b-3812-713c-67e9-9e76c45205e8@lucaceresoli.net>
[-- Attachment #1.1: Type: text/plain, Size: 916 bytes --]
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.
[-- Attachment #1.2: Type: application/pgp-signature, Size: 832 bytes --]
[-- Attachment #2: Type: text/plain, Size: 170 bytes --]
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next prev parent reply other threads:[~2019-10-04 21:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-04 11:04 Remote I/O bus Luca Ceresoli
2019-10-04 13:22 ` Greg KH
2019-10-04 14:08 ` Luca Ceresoli
2019-10-04 14:54 ` Greg KH
2019-10-04 15:08 ` Luca Ceresoli
2019-10-04 21:51 ` Valdis Klētnieks [this message]
2019-10-05 22:29 ` Luca Ceresoli
2019-10-06 0:19 ` Valdis Klētnieks
2019-10-06 9:18 ` Greg KH
2019-10-07 7:48 ` Luca Ceresoli
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=154634.1570225877@turing-police \
--to=valdis.kletnieks@vt.edu \
--cc=greg@kroah.com \
--cc=kernelnewbies@kernelnewbies.org \
--cc=luca@lucaceresoli.net \
/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;
as well as URLs for NNTP newsgroup(s).