title: Loading a android kernel module with vermagic mismatch
body: <p>For a phone there are few modules which are proprietary and aren't licenced under GPL and sources of them are not provided with the kernel sources. So my problem is when I add a custom kernel name or add a upstream patch, there is change in version magic of the kernel and it doesnt match with that of proprietary modules and there is a version magic mismatch for these modules and they don't get loaded.</p>
  
  <p>So is there any workaround for this except manually retaining the vermagic of the kernel with that those of modules? The module is ofcourse compatible with the kernel as it is meant for it, just this vermagic mismatch is causing issue</p>
  
  <p>Also there is no way of force loading a module for an Android kernel. Anyone of you have solution for this?</p>