[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080807140357.ZZRA012@mailhub.coreip.homeip.net>
Date: Thu, 7 Aug 2008 14:11:09 -0400
From: Dmitry Torokhov <dmitry.torokhov@...il.com>
To: Andrew Morton <akpm@...ux-foundation.org>
Cc: torvalds@...ux-foundation.org, rjw@...k.pl, bzolnier@...il.com,
sfr@...b.auug.org.au, linux-next@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-input@...r.kernel.org
Subject: Re: linux-next: Tree for July 30
On Thu, Jul 31, 2008 at 01:10:56PM -0700, Andrew Morton wrote:
>
> If that works then great. But I think the printk could be improved.
> Please provide sufficient information so that users (not programmers)
> can go off and fix things up without needing to email kernel developers.
>
> One suitable approach would be
>
> printk("see http://userweb.kernel.org/~dtor/read-this.txt")
>
Ok, I made a small page here:
http://userweb.kernel.org/~dtor/eviocgbit-bug.html
If you think this is sufficient I'd like to put the patch with the
warning in 2.6.27 so people and distributions could start updarting
affected programs.
--
Dmitry
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists