From: Felipe Balbi <balbi@kernel.org>
To: Chanwoo Choi <cw00.choi@samsung.com>, gregkh@linuxfoundation.org
Cc: linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
linux-omap@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
chanwoo@kernel.org, Chanwoo Choi <cw00.choi@samsung.com>
Subject: Re: [PATCH v2 1/6] usb: dwc3: omap: Replace the extcon API
Date: Mon, 16 Jan 2017 12:31:33 +0200 [thread overview]
Message-ID: <8760lfnvne.fsf@linux.intel.com> (raw)
In-Reply-To: <1483070895-8213-2-git-send-email-cw00.choi@samsung.com>
[-- Attachment #1: Type: text/plain, Size: 423 bytes --]
Hi,
Chanwoo Choi <cw00.choi@samsung.com> writes:
> 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()
>
> Signed-off-by: Chanwoo Choi <cw00.choi@samsung.com>
> Acked-by: Felipe Balbi <felipe.balbi@linux.intel.com>
doesn't apply to testing/next. Please rebase
--
balbi
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2017-01-16 10:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20161230040816epcas5p4616cb93324a5d60bc2a763817e34e37d@epcas5p4.samsung.com>
2016-12-30 4:08 ` [PATCH v2 0/6] usb: Replace the deprecated extcon API Chanwoo Choi
2016-12-30 4:08 ` [PATCH v2 1/6] usb: dwc3: omap: Replace the " Chanwoo Choi
2017-01-16 10:31 ` Felipe Balbi [this message]
2016-12-30 4:08 ` [PATCH v2 2/6] usb: phy: msm: " Chanwoo Choi
2016-12-30 4:08 ` [PATCH v2 3/6] usb: phy: omap-otg: " Chanwoo Choi
2016-12-30 4:08 ` [PATCH v2 4/6] usb: phy: qcom-8x16-usb: " Chanwoo Choi
2016-12-30 4:08 ` [PATCH v2 5/6] usb: phy: tahvo: Replace the deprecated " Chanwoo Choi
2016-12-30 4:08 ` [PATCH v2 6/6] usb: renesas_usbhs: " Chanwoo Choi
2017-01-10 8:18 ` [PATCH v2 0/6] usb: " 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=8760lfnvne.fsf@linux.intel.com \
--to=balbi@kernel.org \
--cc=chanwoo@kernel.org \
--cc=cw00.choi@samsung.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).