From: Greg KH <gregkh@linuxfoundation.org>
To: Chanwoo Choi <cw00.choi@samsung.com>
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: Thu, 11 Oct 2012 11:28:27 +0900 [thread overview]
Message-ID: <20121011022827.GA27117@kroah.com> (raw)
In-Reply-To: <507628C7.9000006@samsung.com>
On Thu, Oct 11, 2012 at 11:02:47AM +0900, Chanwoo Choi wrote:
> On 10/11/2012 10:40 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
> >
> > Linux 3.6 has been released already, I can't take any patches for it. :)
> >
> > Are these for 3.7 instead?
>
> Sorry, The extcon patches are for 3.7.
>
> > And is your gpg key in the public servers so that I "know" this is
> > really the set of patches you want me to pull, and that you are "you"?
> >
> > If you are at LinuxCon Korea the next two days, I'll be glad to sign
> > your key to solve this issue...
> >
>
> OK, Myungjoo Ham and me will attend at LinuxCon Korea tommorrow.
> and will talk to you about gpg key issue.
Ok, I'll hold off on pulling this until after I talk this over with you
in person.
> ps. I will create gpg key and register in public server today.
That will be great. Then you can get a kernel.org git tree as well.
thanks,
greg k-h
next prev parent reply other threads:[~2012-10-11 2:29 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 [this message]
2012-10-18 17:24 ` Greg KH
2012-10-19 1:00 ` Chanwoo Choi
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=20121011022827.GA27117@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=cw00.choi@samsung.com \
--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