From: Pramod Gurav <pramod.gurav@smartplayin.com>
To: Jiri Kosina <jkosina@suse.cz>
Cc: linux-kernel@vger.kernel.org,
Linus Walleij <linus.walleij@linaro.org>,
Alexandre Courbot <gnurou@gmail.com>,
linux-input@vger.kernel.org, linux-gpio@vger.kernel.org
Subject: Re: [PATCH] HID: cp2112: remove use of gpiochip_remove() retval
Date: Wed, 01 Oct 2014 13:49:16 +0530 [thread overview]
Message-ID: <542BB904.1010705@smartplayin.com> (raw)
In-Reply-To: <alpine.LNX.2.00.1410011000450.26311@pobox.suse.cz>
On Wednesday 01 October 2014 01:31 PM, Jiri Kosina wrote:
> On Wed, 1 Oct 2014, Pramod Gurav wrote:
>
>>>>> Cc: Linus Walleij <linus.walleij@linaro.org>
>>>>> Cc: Alexandre Courbot <gnurou@gmail.com>
>>>>> Cc: Jiri Kosina <jkosina@suse.cz>
>>>>> Cc: linux-input@vger.kernel.org
>>>>> Cc: linux-gpio@vger.kernel.org
>>>>>
>>>>> Signed-off-by: Pramod Gurav <pramod.gurav@smartplayin.com>
>>> I guess this depends on some other patch that hasn't gone to Linus yet,
>>> right? As Linus' tree currently has this prototype:
>>>
>>> int gpiochip_remove(struct gpio_chip *chip)
>>
>> Yes. It is yet to make it to linus's tree. But the change is there in
>> linux-next master branch.
>
> Alright. It probably makes most sense to take this patch together with the
> prototype change in one pile (i.e. not through my tree).
>
> For that purpose
>
> Acked-by: Jiri Kosina <jkosina@suse.cz>
Jiri,
Just realized when Linus told me these changes are already in his tree
as well as in mast of linux-tree. Sorry for spaming and late realizing this.
>
prev parent reply other threads:[~2014-10-01 8:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-30 14:24 [PATCH] HID: cp2112: remove use of gpiochip_remove() retval Pramod Gurav
2014-10-01 7:18 ` Jiri Kosina
2014-10-01 7:26 ` Pramod Gurav
2014-10-01 8:01 ` Jiri Kosina
2014-10-01 8:19 ` Pramod Gurav [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=542BB904.1010705@smartplayin.com \
--to=pramod.gurav@smartplayin.com \
--cc=gnurou@gmail.com \
--cc=jkosina@suse.cz \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--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 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).