Michael Gilbert wrote:
> > > another possible solution would be for orinoco.c (which contains the
> > > code that prints these messages) to use the KERN_DEBUG printk level
> > > instead of KERN_INFO.
>
> > i'm wondering why you are reporting this as bug against debian linux-images
> > we have no orinoco specific patch. please discuss that issue upstream
> > on linux-wirel...@vger.kernel.org - any upstream change will directly
> > land into debian.
>
> i reported it here because this is an alternative to the first
> suggestion above (changing the debian default kernel printk level). i
> figured it was up to the kernel maintainers to determine the correct
> solution.
>
> maybe the appropriate solution should be for orinoco.c to only print
> messages to dmesg, rather than to the shell as well as dmesg? i am
> not really that familiar with the kernel -- is there an alternative to
> printk that would do this?
>
> i will also take this upstream. thanks.
What did upstream say? The current orinoco.c log level is still KERN_INFO.
Cheers,
Moritz
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
