-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, 18 Aug 2005, David S. Miller wrote:
From: Jason Wever <[EMAIL PROTECTED]>
Date: Thu, 18 Aug 2005 07:50:58 -0600 (MDT)
Everything looks good now with this patch on both the Blade 100 and Blade
1000. Thanks!
Thanks for testing :-)
Stupid
What does the compiler spit out when drivers/net/ppp_deflate.o
is being built?
I removed the file and reran make. gcc does not say anything and the
later warning stay.
The warnings are actually longer (were before too):
*** Warning: "" [drivers/net/ppp_deflate.ko] undefined!
*** Warning: "" [
From: Jason Wever <[EMAIL PROTECTED]>
Date: Thu, 18 Aug 2005 07:50:58 -0600 (MDT)
> Everything looks good now with this patch on both the Blade 100 and Blade
> 1000. Thanks!
Thanks for testing :-)
Stupid question... have you actually tried to change the
frequency either manually or with a daem
From: Meelis Roos <[EMAIL PROTECTED]>
Date: Thu, 18 Aug 2005 14:50:31 +0300 (EEST)
> Todays 2.6.13-rc6+git tree has broken many modules with warning like
> this on sparc64:
> *** Warning: "current_thread_info_reg" [drivers/net/ppp_deflate.ko] undefined!
>
> These warnings don't go away after mak
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, 17 Aug 2005, David S. Miller wrote:
Jason, give this patch a spin, it should clear up the two
bugs you spotted.
1) The clock tick values given to the cpufreq layer need to be
in KHZ not MHZ.
2) The us2e/us3 drivers were not providing a
Todays 2.6.13-rc6+git tree has broken many modules with warning like
this on sparc64:
*** Warning: "current_thread_info_reg" [drivers/net/ppp_deflate.ko] undefined!
These warnings don't go away after make clean.
--
Meelis Roos ([EMAIL PROTECTED])
-
To unsubscribe from this list: send the line "
On Wed, Aug 17, 2005 at 02:26:09PM -0700, David S. Miller wrote:
> > - if (uart_handle_sysrq_char(&up->port, ch, regs))
> > + if (ch && uart_handle_sysrq_char(&up->port, ch, regs))
>
> uart_handle_sysrq_char() does the "if (ch)" check, you don't
> need to add it here, that's su
