mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Chanwoo Choi <cw00.choi@samsung.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
	linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
	MyungJoo Ham <myungjoo.ham@samsung.com>,
	Kyungmin Park <kyungmin.park@samsung.com>
Subject: [GIT PULL] extcon fixes for 3.13-rc2
Date: Tue, 26 Nov 2013 16:44:08 +0900	[thread overview]
Message-ID: <52945148.2020205@samsung.com> (raw)

Hi Greg,

This is extcon fixes pull request for 3.13-rc2. I add detailed description of
this pull request on below. Please pull extcon fixes with following updates.

The following changes since commit 6ce4eac1f600b34f2f7f58f9cd8f0503d79e42ae:

  Linux 3.13-rc1 (2013-11-22 11:30:55 -0800)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/chanwoo/extcon.git tags/extcon-linus-for-3.13-rc2

for you to fetch changes up to 7585ca0dc950583be7fc62099ca43a0c9551a875:

  extcon: remove freed groups caused the panic or warning in unregister flow (2013-11-26 15:17:23 +0900)

----------------------------------------------------------------
Update extcon for 3.13-rc2

This patchset fix NULL pointer error of extcon-arizona driver and fix issue
about memory of device groups when calling extcon_dev_unregister function.

----------------------------------------------------------------
Charles Keepax (1):
      extcon: arizona: Get pdata from arizona structure not device

Wang, Xiaoming (1):
      extcon: remove freed groups caused the panic or warning in unregister flow

 drivers/extcon/extcon-arizona.c | 4 +---
 drivers/extcon/extcon-class.c   | 3 ++-
 2 files changed, 3 insertions(+), 4 deletions(-)

             reply	other threads:[~2013-11-26  7:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-26  7:44 Chanwoo Choi [this message]
2013-11-27 23: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=52945148.2020205@samsung.com \
    --to=cw00.choi@samsung.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=kyungmin.park@samsung.com \
    --cc=linux-arm-kernel@lists.infradead.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

Powered by JetHome