From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Hn Chen <hn.chen@weidahitech.com>
Cc: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5] Fix the resolution issue in ChromeOS
Date: Thu, 11 Jun 2015 17:41:42 -0700 [thread overview]
Message-ID: <20150612004142.GD20581@dtor-pixel> (raw)
In-Reply-To: <1A63A1423E772B419A9D2E882CBCF6C4020229A8@mail>
Hi Hn,
On Wed, Jun 10, 2015 at 10:41:26PM +0800, Hn Chen wrote:
> Hi, Dmitry,
>
> Thanks for your suggestion !
>
> > Thank you for making changes, I have some more comments. By the way, have you tried running scripts/checkpatch.pl over your patch?
> > It often picks up some common issues.
> I did the check before I submit the patch every time. Below is the way what I did, is it lack of some parameters ?
> ./scripts/checkpatch.pl -f driver/input/touchscreen/wdt87xx_i2c.c
> Or do I check the wrong file ?
I believe --strict option does a few more checks, like having spaces
around operations, argument alignment and so forth.
>
> > Why do you need to disable IRQ here just ti enable it again in probe()?
> Just in case to prevent the IRQ triggered and the input device is not ready.
> After you remind me to create the input device first and then request irq,
> I think they (disable IRQ in request & enable IRQ in probe) can be just removed from codes.
OK good.
Thanks.
--
Dmitry
prev parent reply other threads:[~2015-06-12 9:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-29 4:27 [PATCH v5] Fix the resolution issue in ChromeOS HungNien Chen
2015-05-29 6:56 ` Frans Klaver
[not found] ` <1A63A1423E772B419A9D2E882CBCF6C401F3DB61@mail>
2015-06-01 18:18 ` Frans Klaver
2015-06-10 14:51 ` Hn Chen
2015-06-10 14:51 ` Hn Chen
2015-06-12 10:02 ` Frans Klaver
2015-06-13 7:04 ` Hn Chen
2015-06-13 7:04 ` Hn Chen
2015-06-08 5:56 ` Dmitry Torokhov
2015-06-10 14:41 ` Hn Chen
2015-06-10 14:41 ` Hn Chen
2015-06-12 0:41 ` 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=20150612004142.GD20581@dtor-pixel \
--to=dmitry.torokhov@gmail.com \
--cc=hn.chen@weidahitech.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.