From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Chanwoo Choi <cwchoi00@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Chanwoo Choi <cw00.choi@samsung.com>,
Chanwoo Choi <chanwoo@kernel.org>
Subject: Re: [GIT PULL] extcon next for 6.4
Date: Thu, 27 Apr 2023 16:22:20 +0200 [thread overview]
Message-ID: <2023042729-anthem-canary-4f72@gregkh> (raw)
In-Reply-To: <305aedea-599a-48b0-e3a9-6f71b75e14d8@gmail.com>
On Wed, Apr 26, 2023 at 03:49:17AM +0900, Chanwoo Choi wrote:
> Dear Greg,
>
> On 23. 4. 25. 22:22, Greg Kroah-Hartman wrote:
> > On Tue, Apr 25, 2023 at 09:58:47PM +0900, Chanwoo Choi wrote:
> >> Dear Greg,
> >>
> >> Gently ping for v6.4.
> >
> > Ouch, something went wrong with your first email and it ended up in my
> > spam folder in gmail, so sorry about that :(
>
> I'm sorry. I'll use the @kernel.org account on next time.
>
>
> >
> > Is your tree included in linux-next already?
> >
>
> Yes. extcon.git was included in linux-next.
>
> And my pull request edited the 'class_create()'
> Thus, it might have a conflict as following report[1] from Stetphen Rothwell (linux-next.git).
> [1] https://lore.kernel.org/lkml/ZBhOTW9v9jzJVY7e@kroah.com/
Ok, I've sent off my pull request to Linus now. Let's get that merged
and then I'll take this one and get the class_create() fix in as well.
thanks,
greg k-h
next prev parent reply other threads:[~2023-04-27 14:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-16 15:28 [GIT PULL] extcon next for 6.4 Chanwoo Choi
2023-04-25 12:58 ` Chanwoo Choi
2023-04-25 13:22 ` Greg Kroah-Hartman
2023-04-25 18:49 ` Chanwoo Choi
2023-04-27 14:22 ` Greg Kroah-Hartman [this message]
2023-04-28 6:12 ` Greg Kroah-Hartman
2023-04-30 0:29 ` Chanwoo Choi
2023-04-30 8:00 ` 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=2023042729-anthem-canary-4f72@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=chanwoo@kernel.org \
--cc=cw00.choi@samsung.com \
--cc=cwchoi00@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/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