Andrew Morton wrote:
Please review these patches, queued since 2.6.15-rc1-mm1: ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.15-rc3/2.6.15-rc3-mm1/broken-out/printk-return-value-fix-it.patch ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.15-rc3/2.6.15-rc3-mm1/broken-out/kmsg_write-dont-return-printk-return-value.patch
Yes, those patches actually appear to fix the counting. The patch I submitted merely makes it internally consistent within printk/vprintk(), but does not change it to actually be correct. Cheers - 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/
- References:
- [PATCH] Fix bytecount result from printk()
- From: Mark Lord <[email protected]>
- Re: [PATCH] Fix bytecount result from printk()
- From: Dave Jones <[email protected]>
- Re: [PATCH] Fix bytecount result from printk()
- From: Andrew Morton <[email protected]>
- [PATCH] Fix bytecount result from printk()
- Prev by Date: Re: [PATCH 02/12] mm: supporting variables and functions for balanced zone aging
- Next by Date: Re: [patch 00/43] ktimer reworked
- Previous by thread: Re: [PATCH] Fix bytecount result from printk()
- Next by thread: Re: [PATCH] Fix bytecount result from printk()
- Index(es):
 |