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@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"Chanwoo Choi (chanwoo@kernel.org)" <chanwoo@kernel.org>,
	함명주 <myungjoo.ham@samsung.com>
Subject: Re: [GIT PULL] extcon next for v5.8
Date: Fri, 29 May 2020 17:32:07 +0900	[thread overview]
Message-ID: <c716374a-dac4-11bc-818c-a583f1e1a365@samsung.com> (raw)
In-Reply-To: <20200529080341.GB599635@kroah.com>

Dear Greg,

On 5/29/20 5:03 PM, Greg KH wrote:
> On Fri, May 29, 2020 at 12:11:03PM +0900, Chanwoo Choi wrote:
>> Dear Greg,
>>
>> This is extcon-next pull request for v5.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 9cb1fd0efd195590b828b9b865421ad345a4a145:
>>
>>   Linux 5.7-rc7 (2020-05-24 15:32:54 -0700)
>>
>> are available in the Git repository at:
>>
>>   git://git.kernel.org/pub/scm/linux/kernel/git/chanwoo/extcon.git tags/extcon-next-for-5.8
> 
> As my char-misc-next branch is currently at 5.7-rc5, why did you need to
> make this against -rc7?

I'm sorry. I just checked the 'char-misc-linus' branch
and then made it based on 5.7-rc7. It is my mistake.

I'll make the pull-request based on v5.7-rc5 again.

> 
> Mind if I just rebase your patches against my tree instead of pulling
> the whole thing up to -rc7, or is there some dependancy there that you
> needed to do this?
> 
> thanks,
> 
> greg k-h
> 
> 


-- 
Best Regards,
Chanwoo Choi
Samsung Electronics

      reply	other threads:[~2020-05-29  8:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20200529030043epcas1p2a41f6271b91e086a2e730a488ce53015@epcas1p2.samsung.com>
2020-05-29  3:11 ` Chanwoo Choi
2020-05-29  8:03   ` Greg KH
2020-05-29  8:32     ` Chanwoo Choi [this message]

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=c716374a-dac4-11bc-818c-a583f1e1a365@samsung.com \
    --to=cw00.choi@samsung.com \
    --cc=chanwoo@kernel.org \
    --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

all inboxes | Powered by JetHome®