From: kgene.kim@samsung.com (Kukjin Kim)
To: linux-arm-kernel@lists.infradead.org
Subject: s5p tree moved back to kernel.org
Date: Sat, 19 Nov 2011 00:34:52 +0900 [thread overview]
Message-ID: <4EC67B1C.9050102@samsung.com> (raw)
In-Reply-To: <20111118104248.e792a33685c3d750287d1513@canb.auug.org.au>
On 11/18/11 08:42, Stephen Rothwell wrote:
> Hi,
>
> On Thu, 17 Nov 2011 09:00:30 +0900 Kukjin Kim<kgene.kim@samsung.com> wrote:
>>
>> Could you please change my tree to following?
>>
>> git://git.kernel.org/pub/scm/linux/kernel/git/kgene/linux-samsung.git
>> for-next
>
> I have switched to that.
>
Thanks :)
>> If any problems, please let me know.
>
> The tree on kernel.org appears to have not been updated for the fix that
> appeared overnight.
Oh, I fixed it just now.
Thanks.
Best regards,
Kgene.
--
Kukjin Kim <kgene.kim@samsung.com>, Senior Engineer,
SW Solution Development Team, Samsung Electronics Co., Ltd.
prev parent reply other threads:[~2011-11-18 15:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-17 0:00 s5p tree moved back to kernel.org Kukjin Kim
2011-11-17 23:42 ` Stephen Rothwell
2011-11-18 15:34 ` Kukjin Kim [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=4EC67B1C.9050102@samsung.com \
--to=kgene.kim@samsung.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).