Arjan van de Ven <[email protected]> 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 [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- Re: [2.6 patch] the scheduled removal of the obsolete raw driver
- From: Jesper Juhl <[email protected]>
- Re: [2.6 patch] the scheduled removal of the obsolete raw driver
- From: Arjan van de Ven <[email protected]>
- Re: [2.6 patch] the scheduled removal of the obsolete raw driver
- References:
- [2.6 patch] the scheduled removal of the obsolete raw driver
- From: Adrian Bunk <[email protected]>
- Re: [2.6 patch] the scheduled removal of the obsolete raw driver
- From: Andrew Morton <[email protected]>
- Re: [2.6 patch] the scheduled removal of the obsolete raw driver
- From: Arjan van de Ven <[email protected]>
- Re: [2.6 patch] the scheduled removal of the obsolete raw driver
- From: Dave Jones <[email protected]>
- Re: [2.6 patch] the scheduled removal of the obsolete raw driver
- From: Andrew Morton <[email protected]>
- Re: [2.6 patch] the scheduled removal of the obsolete raw driver
- From: Arjan van de Ven <[email protected]>
- [2.6 patch] the scheduled removal of the obsolete raw driver
- Prev by Date: [PATCH] DocBook: allow even longer return types
- Next by Date: [PATCH] DocBook: fix some comments in drivers/scsi
- Previous by thread: Re: [2.6 patch] the scheduled removal of the obsolete raw driver
- Next by thread: Re: [2.6 patch] the scheduled removal of the obsolete raw driver
- Index(es):
 |