public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chanwoo Choi <chanwoo@kernel.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Chanwoo Choi <cw00.choi@samsung.com>,
	Chanwoo Choi <chanwoo@kernel.org>,
	MyungJoo Ham <myungjoo.ham@samsung.com>
Subject: [GIT PULL] extcon next for 6.8
Date: Tue, 19 Dec 2023 07:40:27 +0900	[thread overview]
Message-ID: <fee142e1-ac58-477f-b8d7-51e108dddbf6@kernel.org> (raw)

Dear Greg,

This is extcon-next pull request for v6.8. 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 b85ea95d086471afb4ad062012a4d73cd328fa86:

  Linux 6.7-rc1 (2023-11-12 16:19:07 -0800)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/chanwoo/extcon.git tags/extcon-next-for-6.8
  
for you to fetch changes up to 7803680964c025f598f827b7ea7433467ef21a56:

  extcon: qcom-spmi-misc: don't use kernel-doc marker for comment (2023-12-12 09:33:47 +0900)

----------------------------------------------------------------
Update extcon next for v6.8

Detailed description for this pull request:
1. Fix possible memory leak of device name in extcon_dev_register()
 : Fix memory leak on error path of extcon_dev_register().

2. Set interrupt polarity based on device-tree for extcon-usbc-tusb320.c
 :Remove 'IRQF_TRIGGER_FALLING' request which is not allowed on
 every interrupt controller (i.e. arm64 GIC). Replace flag by a
 request that depends on the actual device-tree setting.

3. Fix the comment style according to guide on extcon-qcom-spmi-misc.c.
----------------------------------------------------------------

Lukas Funke (1):
      extcon: usbc-tusb320: Set interrupt polarity based on device-tree

Randy Dunlap (1):
      extcon: qcom-spmi-misc: don't use kernel-doc marker for comment

Yaxiong Tian (1):
      extcon: fix possible name leak in extcon_dev_register()

 drivers/extcon/extcon-qcom-spmi-misc.c | 2 +-
 drivers/extcon/extcon-usbc-tusb320.c   | 9 ++++++++-
 drivers/extcon/extcon.c                | 3 +--
 3 files changed, 10 insertions(+), 4 deletions(-)

             reply	other threads:[~2023-12-18 22:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-18 22:40 Chanwoo Choi [this message]
2023-12-19  7:58 ` [GIT PULL] extcon next for 6.8 Greg Kroah-Hartman

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=fee142e1-ac58-477f-b8d7-51e108dddbf6@kernel.org \
    --to=chanwoo@kernel.org \
    --cc=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