From: Chanwoo Choi <cw00.choi@samsung.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"\"최찬우 (samsung.com)\"" <cw00.choi@samsung.com>,
함명주 <myungjoo.ham@samsung.com>
Subject: [GIT PULL] extcon next for v4.19
Date: Thu, 19 Jul 2018 09:17:04 +0900 [thread overview]
Message-ID: <5B4FD880.60806@samsung.com> (raw)
In-Reply-To: CGME20180719001704epcas2p2aab364365a7e3e9e52d619bd612a6958@epcas2p2.samsung.com
Dear Greg,
This is extcon-next pull request for v4.19. 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 ce397d215ccd07b8ae3f71db689aedb85d56ab40:
Linux 4.18-rc1 (2018-06-17 08:04:49 +0900)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/chanwoo/extcon.git tags/extcon-next-for-4.19
for you to fetch changes up to 8a9dbb779fe882325b9a0238494a7afaff2eb444:
extcon: Release locking when sending the notification of connector state (2018-07-12 09:06:31 +0900)
----------------------------------------------------------------
Update extcon for 4.19
Detailed description for this pull request:
1. Release locking when sending the connector state in extcon_sync()
- Previously, extcon used the spinlock before calling the notifier_call_chain
to prevent the scheduled out of task and to prevent the notification delay.
When spinlock is locked for sending the notification, deadlock issue
occured on the side of extcon consumer device. To fix this issue on extcon
consumer device, release locking when sending the connector state.
2. Fix minor issues of extcon provider driver
- extcon-intel-int3496.c uses 'linux/gpio/consumer.h' instead of 'linux/gpio.h'
- extcon-usbc-cors-ec.c adds SPDX license and fix the wrong license information
----------------------------------------------------------------
Chanwoo Choi (1):
extcon: Release locking when sending the notification of connector state
Enric Balletbo i Serra (2):
extcon: usbc-cros-ec: Make license text and module license match.
extcon: usbc-cros-ec: Switch to SPDX identifier.
Wolfram Sang (1):
extcon: int3496: Use proper GPIO include
drivers/extcon/extcon-intel-int3496.c | 2 +-
drivers/extcon/extcon-usbc-cros-ec.c | 22 ++++++----------------
drivers/extcon/extcon.c | 3 ++-
3 files changed, 9 insertions(+), 18 deletions(-)
next parent reply other threads:[~2018-07-19 0:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20180719001704epcas2p2aab364365a7e3e9e52d619bd612a6958@epcas2p2.samsung.com>
2018-07-19 0:17 ` Chanwoo Choi [this message]
2018-07-21 6:13 ` [GIT PULL] extcon next for v4.19 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=5B4FD880.60806@samsung.com \
--to=cw00.choi@samsung.com \
--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;
as well as URLs for NNTP newsgroup(s).