From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: No stable driver/module api?
Date: Sun, 23 Jun 2013 20:13:16 +0200 [thread overview]
Message-ID: <2105177.8kY1vWxy2t@wuerfel> (raw)
In-Reply-To: <CABp-a4eHep=hx7HQ=Og0GC0t=CyE8u2sVt7BwyVMJb9zjA2ePw@mail.gmail.com>
On Sunday 23 June 2013 19:29:52 Per Strandh wrote:
>
> I have now encountered one problem with this layout.
> When upgrading the kernel, our driver in the root file system isn't
> always compatible/loading.
>
> When upgrading from 3.0.18 to 3.0.22 it worked out fine.
> When upgrading from 3.0.22 to 3.0.23 the driver isn't loading.
> When trying to load it if fails with the message:
> - "disagrees about version of symbol module_layout"
>
> We have configured the kernel with the option
> CONFIG_MODULE_FORCE_LOAD=y
>
>
>
> Isn't the driver/module api stable within the 3.0 track?
The API is generally stable, unless there is a serious bug,
the ABI is not. If the API ever changes, you should get a build
warning when recompiling your module.
The easiest way to deal with those changes is to keep your
own code as a patch to the mainline kernel and build it all
together. That also makes it easier for your to show that
you are shipping the matching source code for all the
binary kernel code.
Arnd
next prev parent reply other threads:[~2013-06-23 18:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-23 17:29 No stable driver/module api? Per Strandh
2013-06-23 18:13 ` Arnd Bergmann [this message]
2013-06-23 19:32 ` Russell King - ARM Linux
2013-06-23 22:58 ` Ezequiel Garcia
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=2105177.8kY1vWxy2t@wuerfel \
--to=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.org \
/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