From: Chanwoo Choi <cw00.choi@samsung.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
대인기 <inki.dae@samsung.com>,
"Kyungmin Park" <kyungmin.park@samsung.com>,
"myungjoo.ham@samsung.com" <myungjoo.ham@samsung.com>
Subject: [GIT PULL] extcon fixes for 4.2-rc5
Date: Fri, 31 Jul 2015 16:28:02 +0900 [thread overview]
Message-ID: <55BB2382.3060609@samsung.com> (raw)
Dear Greg,
This is extcon-fixes pull request for v4.2-rc5. I added detailed description
of this pull request on below. Please pull extcon with following fixes.
Best Regards,
Chanwoo Choi
The following changes since commit cbfe8fa6cd672011c755c3cd85c9ffd4e2d10a6f:
Linux 4.2-rc4 (2015-07-26 12:26:21 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/chanwoo/extcon.git tags/extcon-fixes-for-4.2-rc5
for you to fetch changes up to f7a898117aebf3d52370fe637f4d7aff7a237afc:
extcon: Fix extcon_cable_get_state() from getting old state after notification (2015-07-31 15:18:41 +0900)
----------------------------------------------------------------
Update extcon for v4.2-rc5
This patchset fix the following two issue:
- Fix hang issue when using the extcon_[get|set]_cable_state() because these
functions use the cable index instead of cable id.
- Fix NULL pointer error of extcon-palmas.c by removing unneeded kfree() call.
----------------------------------------------------------------
Chanwoo Choi (1):
extcon: palmas: Fix NULL pointer error
Roger Quadros (2):
extcon: Fix hang and extcon_get/set_cable_state().
extcon: Fix extcon_cable_get_state() from getting old state after notification
drivers/extcon/extcon-palmas.c | 13 ---------
drivers/extcon/extcon.c | 61 ++++++++++++++++++++++++++++++------------
2 files changed, 44 insertions(+), 30 deletions(-)
next reply other threads:[~2015-07-31 7:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-31 7:28 Chanwoo Choi [this message]
2015-08-01 0:21 ` [GIT PULL] extcon fixes for 4.2-rc5 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=55BB2382.3060609@samsung.com \
--to=cw00.choi@samsung.com \
--cc=gregkh@linuxfoundation.org \
--cc=inki.dae@samsung.com \
--cc=kyungmin.park@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