Re: [2.6 patch] the scheduled removal of the obsolete raw driver



Arjan van de Ven <arjan@xxxxxxxxxxxxx> wrote:
>
> another thing we really should do is making such "obsolete to be phased
> out" things printk (at least once per boot ;) so that people see it in
> their logs, not just in the kernel source.

Like sys_bdflush() has been doing for 3-4 years. That still comes out on
a few of my test boxes, but I'm a distro recidivist.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/



Relevant Pages

  • Re: [patch] Re: 2.6.16-rc4-mm1 (bugs and lockups)
    ... This is enough for printk but not for the boot lockup. ... The attached patch is however enough. ... +static void boot_cpu_init ...
    (Linux-Kernel)
  • Re: oops pauser. / boot_delayer
    ... >>> This one delays each printkduring boot by a variable time ... Another very common situation is a system which fails to boot due to ... failures to find the root filesystem. ... An option to pause briefly after each boot time printk would be very ...
    (Linux-Kernel)
  • Re: Weird: 30 sec delay during early boot
    ... >>then will proceed to boot successfully and function correctly. ... >>So, 30 seconds with no printk output, then boots normally. ... send the line "unsubscribe linux-kernel" in ...
    (Linux-Kernel)
  • Re: Weird partititon recocnising problem in 2.6.0-testX
    ... > inserted printk stuff. ... Now it really does partition reading. ... Device Boot Start End Blocks Id System ... send the line "unsubscribe linux-kernel" in ...
    (Linux-Kernel)
  • Re: 2.6.15 and CONFIG_PRINTK_TIME
    ... On Wednesday 11 January 2006 08:34, Kalin KOZHUHAROV wrote: ... > I remember there was some talk about resetting the time on printk during the ... > boot to zero... ...
    (Linux-Kernel)