From: Greg KH <gregkh@linuxfoundation.org>
To: Chanwoo Choi <cw00.choi@samsung.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Chanwoo Choi (chanwoo@kernel.org)" <chanwoo@kernel.org>,
함명주 <myungjoo.ham@samsung.com>
Subject: Re: [GIT PULL] extcon next for v5.4
Date: Tue, 3 Sep 2019 21:46:57 +0200 [thread overview]
Message-ID: <20190903194657.GA13390@kroah.com> (raw)
In-Reply-To: <4c61ce13-69c7-f6ce-ae37-722f370371f4@samsung.com>
On Mon, Aug 26, 2019 at 11:55:13AM +0900, Chanwoo Choi wrote:
> Dear Greg,
>
> This is extcon-next pull request for v5.4. I add detailed description of
> this pull request on below. Please pull extcon with following updates.
>
>
> Detailed description for this pull request:
> 1. Clean up the and fix the minor issue of extcon provider driver
> - extcon-arizona/max77843 replace the helper function
> with more correct helper function without operation changes.
> - extcon-fsa9480 supports the FSA880 variant by adding the compatible name.
> - extcon-arizona updates the dt-binding file for the readability.
> - extcon-gpio initializes the interrupt flags according to active-low state.
> - Clean up extcon-sm5502/axp288/adc-jack
>
> Best Regards,
> Chanwoo Choi
>
>
> The following changes since commit 5f9e832c137075045d15cd6899ab0505cfb2ca4b:
>
> Linus 5.3-rc1 (2019-07-21 14:05:38 -0700)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/chanwoo/extcon.git tags/extcon-next-for-5.4
Pulled and pushed out, thanks.
greg k-h
prev parent reply other threads:[~2019-09-03 19:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20190826025109epcas1p2add5354e4989028cd942b2121447dfd8@epcas1p2.samsung.com>
2019-08-26 2:55 ` [GIT PULL] extcon next for v5.4 Chanwoo Choi
2019-09-03 2:49 ` Chanwoo Choi
2019-09-03 19:46 ` Greg KH [this message]
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=20190903194657.GA13390@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=chanwoo@kernel.org \
--cc=cw00.choi@samsung.com \
--cc=linux-kernel@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