From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: 함명주 <myungjoo.ham@samsung.com>
Cc: Axel Lin <axel.lin@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Mike Lockwood <lockwood@android.com>,
"myungjoo.ham@gmail.com" <myungjoo.ham@gmail.com>
Subject: Re: [PATCH 1/2] extcon: Set platform drvdata in gpio_extcon_probe() and fix irq leak
Date: Tue, 19 Jun 2012 09:43:59 -0700 [thread overview]
Message-ID: <20120619164359.GA4571@kroah.com> (raw)
In-Reply-To: <22448380.601061340101146820.JavaMail.weblogic@epml24>
On Tue, Jun 19, 2012 at 10:19:07AM +0000, 함명주 wrote:
> > Add missing platform_set_drvdata() in gpio_extcon_probe(), otherwise calling
> > platform_get_drvdata in gpio_extcon_remove() returns NULL.
> >
> > Also add missing free_irq call in gpio_extcon_remove().
> >
> > Signed-off-by: Axel Lin <axel.lin@gmail.com>
>
> Thanks!
>
>
> Acked-by: MyungJoo Ham <myungjoo.ham@samsung.com>
>
> I'll apply this patch to the extcon-for-next.
> I would appear in http://git.infradead.org/users/kmpark/linux-samsung/shortlog/refs/heads/extcon-for-next soon after syncing servers.
Does this mean you are going to have a separate extcon git tree
somewhere, feeding into linux-next, and sending stuff directly to Linus?
I don't see an entry in the MAINTAINERS file saying this, which is why I
was picking up extcon patches, should I not be doing this?
confused,
greg k-h
next prev parent reply other threads:[~2012-06-19 16:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-19 10:19 [PATCH 1/2] extcon: Set platform drvdata in gpio_extcon_probe() and fix irq leak 함명주
2012-06-19 10:32 ` Axel Lin
2012-06-19 16:43 ` Greg Kroah-Hartman [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-06-16 3:55 Axel Lin
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=20120619164359.GA4571@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=axel.lin@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lockwood@android.com \
--cc=myungjoo.ham@gmail.com \
--cc=myungjoo.ham@samsung.com \
/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