linux-kernel - Re: Re: [PATCH 1/2] extcon: Set platform drvdata in gpio_extcon

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20120620150708.GA13770@kroah.com>
Date:	Wed, 20 Jun 2012 08:07:08 -0700
From:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:	MyungJoo Ham <myungjoo.ham@...sung.com>
Cc:	Axel Lin <axel.lin@...il.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Mike Lockwood <lockwood@...roid.com>,
	"myungjoo.ham@...il.com" <myungjoo.ham@...il.com>,
	"kyungmin.park@...sung.com" <kyungmin.park@...sung.com>,
	"cw00.choi@...sung.com" <cw00.choi@...sung.com>
Subject: Re: Re: [PATCH 1/2] extcon: Set platform drvdata in
 gpio_extcon_probe() and fix irq leak

On Wed, Jun 20, 2012 at 04:32:06AM +0000, MyungJoo Ham wrote:
> > 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@...il.com>
> > > 
> > > Thanks!
> > > 
> > > 
> > > Acked-by: MyungJoo Ham <myungjoo.ham@...sung.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
> > 
> 
> You are right. We do not have MAINTAINERS entry for extcon.

You can easily fix that (hint, hint, hint...)

> I can wait until we have MAINTAINERS entry registered for extcon,
> which we have not request or submit, yet. Until then, I think you may
> pick up the extcon patches and I will simply follow your repositories
> (keep rebasing from yours)

My trees never need rebasing, why would you need to do that?  What is
going into your tree that isn't in mine?  Am I missing patches?

I would be very glad for you to take over this maintainership, if it's
something you want to do, otherwise I have no problem taking the
patches.  It's up to you.

thanks,

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/