From: Chanwoo Choi <cw00.choi@samsung.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"myungjoo.ham@samsung.com" <myungjoo.ham@samsung.com>,
Kyungmin Park <kyungmin.park@samsung.com>
Subject: Re: [GIT PULL] extcon fixes for Linux 3.6
Date: Fri, 19 Oct 2012 10:00:15 +0900 [thread overview]
Message-ID: <5080A61F.1080206@samsung.com> (raw)
In-Reply-To: <20121018172403.GA29562@kroah.com>
On 10/19/2012 02:24 AM, Greg KH wrote:
> On Thu, Oct 11, 2012 at 10:31:19AM +0900, Chanwoo Choi wrote:
>> Hi Greg,
>>
>> Please pull extcon fixes for Linux 3.6 from:
>>
>> git://git.infradead.org/users/kmpark/linux-samsung extcon-for-next
>>
>> I've been creating "extcon-for-next" tree at git.infradead.org
>> and rebasing the branch base on your
>> driver-core.git(branch:driver-core-next).
>>
>> This tree contains various small bugfixes and enhancements, fix typos.
>> And extcon-max77693 initialize MUIC register during probe()
>> to unmask internal interrupt of max77693 MUIC device.
>
> Now that you have a kernel.org account, can you move this tree to
> git.kernel.org, and provide me a signed tag to pull from for this set of
> patches to go into 3.7?
>
OK, I will move extcon tree to git.kernel.org when extcon git repository is created
and request pull extcon patches with a signed tag from extcon tree to go into 3.7.
Best Regards,
Chanwoo Choi
prev parent reply other threads:[~2012-10-19 1:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-11 1:31 [GIT PULL] extcon fixes for Linux 3.6 Chanwoo Choi
2012-10-11 1:40 ` Greg KH
2012-10-11 2:02 ` Chanwoo Choi
2012-10-11 2:28 ` Greg KH
2012-10-18 17:24 ` Greg KH
2012-10-19 1:00 ` 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=5080A61F.1080206@samsung.com \
--to=cw00.choi@samsung.com \
--cc=gregkh@linuxfoundation.org \
--cc=kyungmin.park@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