On 09/12/2013 09:40 AM, Raffaele Morelli wrote:
2013/9/12 Jeremy Jongepier
<jeremy(a)autostatic.com>om>:
On 09/12/2013 07:16 AM, Raffaele Morelli wrote:
2013/9/11 Marco Donnarumma
<devel(a)thesaddj.com>
In 4th reply: `cp /boot/config-$(uname -r) .config && make oldconfig`
this is quite unnecessary as `make oldconfig` will prompt you for
newer configs not found in your current kernel configuration, moreover
make-kpkg does run `make oldconfig` before start compiling.
/r
True but you still need to run make oldconfig somehow otherwise you end
up with the Preemption Model of the original config you're using.
Best,
Jeremy
Quote from man page:
Normally, if kernel-package does not find a .config file in the current
directory, it tries very hard to get an appropriate one (usually a con-
fig file already tailored for Debian kernels for that architecture),
and then calls make oldconfig to let the user answer any new questions.
So if you apply the RT patch, make-kpkg will ask you about preemption model.
/r
Yes I know but I didn't formulate my earlier e-mail well enough. What I
mean is that you still need to run make oldconfig, be it separately or
be it via make-kpkg. When I think about it I wondered why I replied in
the first place, your mail explains it all. Sorry for the noise :-|
Jeremy