On Tue, Nov 04, 2014 at 09:55:14AM +0100, Mike Looijmans wrote:
ïOn 11/03/2014 06:38 PM, Mike Looijmans wrote:
You need to develop against current versions of the kernel, this is
something that was merged into Linus' tree during the merge window.
Is this an absolute show-stopper for you?
With some effort I could move from our current 3.15 to 3.17, but even that
wouldn't be recent enough then. I can justify spending a few days on getting
the driver integrated into mainline, even if the initial version cost less
than that; but moving everything to mainline is going to take weeks and the
boss is definitely going to say "no" to that.
It should be easy to backport the support into your current kernel, it's
just a few commits and there hasn't been much development in this area
of the code. Can you take a look at doing that please?
More important than that: Since this chip powers the IO banks, we need it
for our own products, and hence it has to work (also) on the current 3.15
kernel. Using APIs from 3.18 wouold render the driver useless to ourselves.
This is just not at all important upstream, sorry. The kernel moves on
and internal APIs within the kernel move on so it is expected that code
used in production won't be the latest and greatest upstream code.