linux-kernel - Re: [PATCH 1/5] usb: dwc3: omap: Replace deprecated API of 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]

Date:	Fri, 10 Jul 2015 17:53:50 +0200
From:	Chanwoo Choi <cwchoi00@...il.com>
To:	Felipe Balbi <balbi@...com>
Cc:	Greg KH <gregkh@...uxfoundation.org>,
	linux-kernel <linux-kernel@...r.kernel.org>,
	linux-usb@...r.kernel.org,
	"myungjoo.ham@...sung.com" <myungjoo.ham@...sung.com>
Subject: Re: [PATCH 1/5] usb: dwc3: omap: Replace deprecated API of extcon

Hi Felipe,

On Mon, Jul 6, 2015 at 7:23 PM, Felipe Balbi <balbi@...com> wrote:
> On Wed, Jul 01, 2015 at 01:11:30PM +0900, Chanwoo Choi wrote:
>> This patch removes the deprecated notifier API of extcon framwork
>> and then use the new extcon API with the unique id to indicate
>> the each external connector (USB, USB-HOST).
>>
>> Alter deprecated API as following:
>> - extcon_register_interest() -> extcon_register_notifier()
>> - extcon_get_cable_state(*edev, char *) -> extcon_get_cable_state_(*edev, id)
>>
>> Cc: Felipe Balbi <balbi@...com>
>> Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
>> Signed-off-by: Chanwoo Choi <cw00.choi@...sung.com>
>
> Are there any dependences for this commit or can I take it through my
> tree for v4.3 ?

This patch-set is based on v4.2-rc1 without any dependency.
I agree about your opinion.

I'm sorry about delayed reply because I'm on vacation.

Thanks,
Chanwoo Choi
--
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/