From: MyungJoo Ham <myungjoo.ham@samsung.com>
To: "Greg KH" <gregkh@linuxfoundation.org>, 최찬우 <cw00.choi@samsung.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
박경민 <kyungmin.park@samsung.com>
Subject: Re: Re: [GIT PULL] extcon fixes for Linux 3.6
Date: Fri, 19 Oct 2012 02:02:07 +0000 (GMT) [thread overview]
Message-ID: <24564518.187951350612127085.JavaMail.weblogic@epml28> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=euc-kr, Size: 1266 bytes --]
Sender : Greg KH<gregkh@linuxfoundation.org>
Date : 2012-10-19 02:24 (GMT+09:00)
> 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?
>
> thanks,
>
> greg k-h
>
>
Hello,
Unfortunately, the corporate security managers have been blocking
accessing ssh of *.kernel.org and I'm still dealing with them.
I'll try my best to resolve the issue and move the tree to kernel.org
today.
Thank you.
Cheers!
MyungJoo
ÿôèº{.nÇ+·®+%Ëÿ±éݶ\x17¥wÿº{.nÇ+·¥{±þG«éÿ{ayº\x1dÊÚë,j\a¢f£¢·hïêÿêçz_è®\x03(éÝ¢j"ú\x1a¶^[m§ÿÿ¾\a«þG«éÿ¢¸?¨èÚ&£ø§~á¶iOæ¬z·vØ^\x14\x04\x1a¶^[m§ÿÿÃ\fÿ¶ìÿ¢¸?I¥
reply other threads:[~2012-10-19 2:02 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=24564518.187951350612127085.JavaMail.weblogic@epml28 \
--to=myungjoo.ham@samsung.com \
--cc=cw00.choi@samsung.com \
--cc=gregkh@linuxfoundation.org \
--cc=kyungmin.park@samsung.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