From: Chanwoo Choi <cw00.choi@samsung.com>
To: gregkh@linuxfoundation.org
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"\"최찬우 (samsung.com)\"" <cw00.choi@samsung.com>,
"Chanwoo Choi (chanwoo@kernel.org)" <chanwoo@kernel.org>,
함명주 <myungjoo.ham@samsung.com>
Subject: [GIT PULL] extcon next for v4.20
Date: Mon, 01 Oct 2018 19:14:06 +0900 [thread overview]
Message-ID: <5BB1F36E.9090804@samsung.com> (raw)
In-Reply-To: CGME20181001101407epcas2p133c98fcd05385608a2a5d2dca859f6cb@epcas2p1.samsung.com
Dear Greg,
This is extcon-next pull request for v4.20. I add detailed description of
this pull request on below. Please pull extcon with following updates.
Best Regards,
Chanwoo Choi
The following changes since commit 5b394b2ddf0347bef56e50c69a58773c94343ff3:
Linux 4.19-rc1 (2018-08-26 14:11:59 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/chanwoo/extcon.git tags/extcon-next-for-4.20
for you to fetch changes up to 2e464ff0a9b1ab0fbb56e2ca8b1f5ff8c9f4e02f:
extcon: int3496: Convert to use SPDX identifier (2018-08-28 11:21:15 +0900)
----------------------------------------------------------------
Update extcon for 4.20
Detailed description for this pull request:
1. Add SPDX license identifiers for Maxim and Intel extcon drivers
2. Clean-up extcon-intel-cht-wc.c driver without operation changes
3. Fix build warning of extcon core and use kasprintf instead of snprintf
----------------------------------------------------------------
Andy Shevchenko (7):
extcon: Make static analyzer happy about union assignment
extcon: Switch to use kasprintf() instead of open coded
extcon: cht-wc: Return from default case to avoid warnings
extcon: cht-wc: Fix definition names according to spec
extcon: cht-wc: Correct USBID bit field handling
extcon: cht-wc: Convert to use SPDX identifier
extcon: int3496: Convert to use SPDX identifier
Krzysztof Kozlowski (1):
extcon: maxim: Add SPDX license identifiers
drivers/extcon/extcon-intel-cht-wc.c | 60 +++++++++++++++++------------------
drivers/extcon/extcon-intel-int3496.c | 12 ++-----
drivers/extcon/extcon-max14577.c | 24 ++++----------
drivers/extcon/extcon-max77693.c | 22 ++++---------
drivers/extcon/extcon-max77843.c | 19 ++++-------
drivers/extcon/extcon-max8997.c | 22 ++++---------
drivers/extcon/extcon.c | 15 +++------
7 files changed, 61 insertions(+), 113 deletions(-)
next parent reply other threads:[~2018-10-01 10:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20181001101407epcas2p133c98fcd05385608a2a5d2dca859f6cb@epcas2p1.samsung.com>
2018-10-01 10:14 ` Chanwoo Choi [this message]
2018-10-02 0:42 ` [GIT PULL] extcon next for v4.20 Greg KH
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=5BB1F36E.9090804@samsung.com \
--to=cw00.choi@samsung.com \
--cc=chanwoo@kernel.org \
--cc=gregkh@linuxfoundation.org \
--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