The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Chanwoo Choi <chanwoo@kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Chanwoo Choi <cw00.choi@samsung.com>,
	MyungJoo Ham <myungjoo.ham@samsung.com>
Subject: Re: [GIT PULL] extcon next for 6.17
Date: Sat, 26 Jul 2025 08:53:50 +0200	[thread overview]
Message-ID: <2025072609-knapsack-drinking-c979@gregkh> (raw)
In-Reply-To: <15ca3763-45a5-40af-93a8-449a9f1f33a9@kernel.org>

On Sat, Jul 26, 2025 at 09:34:47AM +0900, Chanwoo Choi wrote:
> Dear Greg,
> 
> This is extcon-next pull request. 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 86731a2a651e58953fc949573895f2fa6d456841:
> 
>   Linux 6.16-rc3 (2025-06-22 13:30:08 -0700)
> 
> are available in the Git repository at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/chanwoo/extcon.git tags/extcon-next-for-6.17
> 
> for you to fetch changes up to 5f09caafc652bcee7a5247e40dd34d1de1ad7d7f:
> 
>   extcon: fsa9480: Avoid buffer overflow in fsa9480_handle_change() (2025-07-19 12:39:13 +0900)

My tree is closed now, sorry.  Can you break this up into different pull
requests after -rc1 is out, one for bugfixes, and one for new features
for 6.18-rc1?

thanks,

greg k-h

  reply	other threads:[~2025-07-26  6:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-26  0:34 [GIT PULL] extcon next for 6.17 Chanwoo Choi
2025-07-26  6:53 ` Greg Kroah-Hartman [this message]
2025-08-01 13:31   ` Chanwoo Choi

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=2025072609-knapsack-drinking-c979@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=chanwoo@kernel.org \
    --cc=cw00.choi@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