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 for Android: free password hash cracker in your pocket
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-id: <25919571.619021340166725967.JavaMail.weblogic@epml24>
Date:	Wed, 20 Jun 2012 04:32:07 +0000 (GMT)
From:	MyungJoo Ham <myungjoo.ham@...sung.com>
To:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>
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 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.

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)

Sorry for the confusion.


MyungJoo



Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ