From: dmitry.torokhov@gmail.com (Dmitry Torokhov)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 2/2] Input: ads7846: use gpio_request_one to configure pendown_gpio
Date: Fri, 4 Feb 2011 08:09:12 -0800 [thread overview]
Message-ID: <20110204160912.GA11723@core.coreip.homeip.net> (raw)
In-Reply-To: <4D4C1D39.5080208@compulab.co.il>
Hi,
On Fri, Feb 04, 2011 at 05:37:29PM +0200, Igor Grinberg wrote:
> Hi,
>
> On 02/04/11 17:15, G, Manjunath Kondaiah wrote:
>
> > On Fri, Feb 04, 2011 at 04:47:09PM +0200, Igor Grinberg wrote:
> >> On 02/04/11 16:16, G, Manjunath Kondaiah wrote:
> >>> On Fri, Feb 04, 2011 at 03:08:47PM +0100, Wolfram Sang wrote:
> >>>> On Fri, Feb 04, 2011 at 07:02:50PM +0530, G, Manjunath Kondaiah wrote:
> >>>>> On Thu, Feb 03, 2011 at 09:19:53AM -0800, Dmitry Torokhov wrote:
> >>>>>> Something like below should do I think.
> >>>>> Patch looks good but it applies only on top of previous patch:
> >>>>> https://patchwork.kernel.org/patch/529941/
> >>>>>
> >>>>> Why to have two patches for this fix?
> >>>> http://www.spinics.net/lists/linux-omap/msg45167.html
> >>> My point here is:
> >>> 1. The first patch only replaces gpio_request with gpio_request_one
> >>> 2. Rest of the things are handled in 2nd patch posted by dmitry
> >>>
> >>> What is harm in merging both the patches? I don't think it affects
> >>> readability.
I kept 2 patches because they solve 2 different problems.
> >> Because the changes introduced by the patches are from different nature.
> >> As stated in the link above, one is a functional change (gpio setup change)
> >> and second is fixing the imbalance in request - free calls.
> >> The impact is not readability, but bad bisect-ability.
> > ok. But the patch2(dmitry's patch) is doing more than what it is mentioned in
> > patch description. It checks for validity of gpio, comment correction
> > etc which needs to be updated in the patch description.
I am pretty sure I expanded on the scope of the change in the body of the
changelog.
>
> gpio validity is a part of request - free balance fix, comment change is
> just a coding style fix - really minor.
>
> Personally, I think Dmitry's description of the patch is just fine,
> but if you insist on making it somehow better, then suggest it to Dmitry.
The both patches are already in my public branch so patch description is
set.
Thanks.
--
Dmitry
next prev parent reply other threads:[~2011-02-04 16:09 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-03 15:21 [PATCH v3 2/2] Input: ads7846: use gpio_request_one to configure pendown_gpio Sourav Poddar
2011-02-03 16:54 ` Dmitry Torokhov
2011-02-03 17:19 ` Dmitry Torokhov
2011-02-03 22:12 ` Wolfram Sang
2011-02-04 8:05 ` Varadarajan, Charulatha
2011-02-04 12:59 ` Poddar, Sourav
2011-02-04 13:32 ` G, Manjunath Kondaiah
2011-02-04 13:37 ` Kishore Kadiyala
2011-02-04 13:41 ` G, Manjunath Kondaiah
2011-02-04 14:08 ` Wolfram Sang
2011-02-04 14:16 ` G, Manjunath Kondaiah
2011-02-04 14:47 ` Igor Grinberg
2011-02-04 15:11 ` Poddar, Sourav
2011-02-04 15:30 ` Igor Grinberg
2011-02-05 6:59 ` Poddar, Sourav
2011-02-06 7:31 ` Igor Grinberg
2011-02-04 15:15 ` G, Manjunath Kondaiah
2011-02-04 15:37 ` Igor Grinberg
2011-02-04 16:09 ` Dmitry Torokhov [this message]
2011-02-04 14:54 ` Wolfram Sang
2011-02-04 15:13 ` Igor Grinberg
2011-02-03 17:05 ` Wolfram Sang
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=20110204160912.GA11723@core.coreip.homeip.net \
--to=dmitry.torokhov@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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).