mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Chanwoo Choi <cwchoi00@gmail.com>
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>
Subject: Re: [GIT PULL] extcon next for 6.4
Date: Sun, 30 Apr 2023 09:29:39 +0900	[thread overview]
Message-ID: <1d060b2a-84b5-a3e7-c97d-ac656f244811@gmail.com> (raw)
In-Reply-To: <ZEtj1oWqBlmgwc2b@kroah.com>

On 23. 4. 28. 15:12, Greg Kroah-Hartman wrote:
> 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 tried to pull this today, but I get the following error:
> 
> Commit: 40f9fc3c2b38 ("extcon: usbc-tusb320: add USB_ROLE_SWITCH dependency")
> 	Fixes tag: Fixes: 19685ae43489 ("extcon: usbc-tusb320: add usb_role_switch support")
> 	Has these problem(s):
> 		- Target SHA1 does not exist
> 
> Are you sure that linux-next actually passed this tree?
> 
> All of these were added to your tree only 12 days ago.  Perhaps we should just
> wait until 6.5-rc1 for the new features, and take the bug fixes now?  Can you
> redo this to make it so I can take the bugfixes after 6.4-rc1 is out, and throw
> away this tree for now?

Dear Greg,

I'm so sorry for my fault. I rebased extcon-next tree based on char-misc.git(v6.3-rc6)
right before sending the pull request. It it the reason to be changed of the commit id.

I'll fix issue and then send the pull request for 6.5-rc1 on later. I'll not rebase
the extcon branch before sending the pull request and use the kernel.org email.

Once again, I'm sorry to bother you.

-- 
Best Regards,
Samsung Electronics
Chanwoo Choi


  reply	other threads:[~2023-04-30  0:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-16 15:28 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
2023-04-28  6:12       ` Greg Kroah-Hartman
2023-04-30  0:29         ` Chanwoo Choi [this message]
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=1d060b2a-84b5-a3e7-c97d-ac656f244811@gmail.com \
    --to=cwchoi00@gmail.com \
    --cc=chanwoo@kernel.org \
    --cc=cw00.choi@samsung.com \
    --cc=gregkh@linuxfoundation.org \
    --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

all inboxes | Powered by JetHome®