From: Chanwoo Choi <cw00.choi@samsung.com>
To: Kishon Vijay Abraham I <kishon@ti.com>,
balbi@kernel.org, gregkh@linuxfoundation.org
Cc: linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-usb@vger.kernel.org,
chanwoo@kernel.org, myungjoo.ham@samsung.com,
linux-rockchip@lists.infradead.org
Subject: Re: [PATCH 2/5] phy: rockchip-inno-usb2: Replace the extcon API
Date: Thu, 03 Aug 2017 17:11:22 +0900 [thread overview]
Message-ID: <5982DAAA.8060201@samsung.com> (raw)
In-Reply-To: <06154871-a821-edab-23d8-340c5b0f5081@ti.com>
Hi,
On 2017년 08월 02일 14:12, Kishon Vijay Abraham I wrote:
>
>
> On Monday 17 July 2017 06:50 AM, Chanwoo Choi wrote:
>> This patch uses the resource-managed extcon API for extcon_register_notifier()
>> and replaces the deprecated extcon API as following:
>> - extcon_get_cable_state_() -> extcon_get_state()
>> - extcon_set_cable_state_() -> extcon_set_state_sync()
>>
>> Cc: linux-rockchip@lists.infradead.org
>> acked-by: Kishon Vijay Abraham I <kishon@ti.com>
> ^
> should be 'A' here.
My mistake. I'll fix it.
[snip]
--
Best Regards,
Chanwoo Choi
Samsung Electronics
next prev parent reply other threads:[~2017-08-03 8:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20170717012057epcas1p11fe3d445ed16c7f94b57922b0a8f243a@epcas1p1.samsung.com>
2017-07-17 1:20 ` [PATCH 0/5] phy: Replace the deprecated extcon API Chanwoo Choi
2017-07-17 1:20 ` [PATCH 1/5] phy: qcom-usb-hs: Replace the " Chanwoo Choi
2017-07-17 1:20 ` [PATCH 2/5] phy: rockchip-inno-usb2: " Chanwoo Choi
2017-08-02 5:12 ` Kishon Vijay Abraham I
2017-08-03 8:11 ` Chanwoo Choi [this message]
2017-07-17 1:20 ` [PATCH 3/5] phy: phy-bcm-ns2-usbdrd: Replace the deprecated " Chanwoo Choi
2017-08-02 5:12 ` Kishon Vijay Abraham I
2017-07-17 1:20 ` [PATCH 4/5] usb: gadget: udc: " Chanwoo Choi
2017-07-17 1:20 ` [PATCH 5/5] extcon: Remove deprecated extcon_set/get_cable_state_() Chanwoo Choi
2017-07-31 1:48 ` [PATCH 0/5] phy: Replace the deprecated extcon API Chanwoo Choi
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=5982DAAA.8060201@samsung.com \
--to=cw00.choi@samsung.com \
--cc=balbi@kernel.org \
--cc=chanwoo@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=kishon@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=linux-usb@vger.kernel.org \
--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