From: Dmitry Torokhov <dtor@insightbb.com>
To: Parag Warudkar <parag.warudkar@gmail.com>
Cc: linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
akpm@linux-foundation.org
Subject: Re: [PATCH] TSDEV - Don't flood dmesg with removal warnings
Date: Sun, 29 Jul 2007 00:37:36 -0400 [thread overview]
Message-ID: <200707290037.37606.dtor@insightbb.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0707271038100.5691@parag-desktop>
Hi Parag,
On Friday 27 July 2007 10:43, Parag Warudkar wrote:
> Ignore my previous whitespace damaged patch. This one should be good.
>
> tsdev.c warns about scheduled removal each time tsdev_open is called -
> So even for a default boot I get to see the warning 3 times -
>
> [ 340.537078] tsdev (compaq touchscreen emulation) is scheduled for
> removal.
> [ 340.537081] See Documentation/feature-removal-schedule.txt for details.
> [ 340.550314] tsdev (compaq touchscreen emulation) is scheduled for
> removal.
> [ 340.550318] See Documentation/feature-removal-schedule.txt for details.
> [ 340.565065] tsdev (compaq touchscreen emulation) is scheduled for
> removal.
> [ 340.565068] See Documentation/feature-removal-schedule.txt for details.
>
> Move the warning to tsdev_init() from tsdev_open so we don't end up
> printing a large string in dmesg everytime tsdev_open is called.
>
The printk was moved per Andrew's request to make it more annoying.
Obviously it is working ;) Do you know what is opening /dev/input/tsX
nodes?
--
Dmitry
next prev parent reply other threads:[~2007-07-29 4:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-27 14:43 [PATCH] TSDEV - Don't flood dmesg with removal warnings Parag Warudkar
2007-07-29 4:37 ` Dmitry Torokhov [this message]
2007-07-29 13:58 ` Parag Warudkar
-- strict thread matches above, loose matches on Subject: below --
2007-07-27 14:09 Parag Warudkar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200707290037.37606.dtor@insightbb.com \
--to=dtor@insightbb.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=parag.warudkar@gmail.com \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox