From: Dan Carpenter <dan.carpenter@oracle.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Henrik Rydberg <rydberg@euromail.se>,
Ping Cheng <pingc@wacom.com>,
Peter Hutterer <peter.hutterer@who-t.net>,
Aristeu Rozanski <aris@ruivo.org>,
linux-input@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [patch] Input: potential info leak in uiput_ff_upload_to_user()
Date: Fri, 23 Sep 2011 10:31:52 +0300 [thread overview]
Message-ID: <20110923073152.GG29426@longonot.mountain> (raw)
In-Reply-To: <20110923062240.GG4387@elgon.mountain>
This one is wrong as well. I suck. :/
regards,
dan carpenter
prev parent reply other threads:[~2011-09-23 7:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-23 6:22 [patch] Input: potential info leak in uiput_ff_upload_to_user() Dan Carpenter
2011-09-23 7:30 ` Dmitry Torokhov
2011-09-23 7:31 ` Dan Carpenter [this message]
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=20110923073152.GG29426@longonot.mountain \
--to=dan.carpenter@oracle.com \
--cc=aris@ruivo.org \
--cc=dmitry.torokhov@gmail.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=peter.hutterer@who-t.net \
--cc=pingc@wacom.com \
--cc=rydberg@euromail.se \
/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;
as well as URLs for NNTP newsgroup(s).