From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Ondrej Zary <linux@rainbow-software.org>
Cc: linux-input@vger.kernel.org
Subject: Re: [PATCH] Input: usbtouchscreen - reduce number fo be16_to_cpu conversions
Date: Fri, 4 Jun 2010 09:24:10 -0700 [thread overview]
Message-ID: <20100604162410.GA16827@core.coreip.homeip.net> (raw)
In-Reply-To: <201006041235.03153.linux@rainbow-software.org>
On Fri, Jun 04, 2010 at 12:35:02PM +0200, Ondrej Zary wrote:
> On Friday 04 June 2010, Dmitry Torokhov wrote:
> > Let's perform be16_to_cpu() conversions once for each received packet,
> > and then use cached values. Makes code a little bit easier to follow.
> >
> > Signed-off-by: Dmitry Torokhov <dtor@mail.ru>
> > ---
> >
> > Ondrej,
> >
> > Any chance you could test the following patch?
>
> Thanks for the patch, it works.
>
Thanks Ondrej, I'll queue it for .36 then.
--
Dmitry
prev parent reply other threads:[~2010-06-04 16:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-04 7:51 [PATCH] Input: usbtouchscreen - reduce number fo be16_to_cpu conversions Dmitry Torokhov
2010-06-04 10:35 ` Ondrej Zary
2010-06-04 16:24 ` Dmitry Torokhov [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=20100604162410.GA16827@core.coreip.homeip.net \
--to=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux@rainbow-software.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;
as well as URLs for NNTP newsgroup(s).