From: Kukjin Kim <kgene.kim@samsung.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
Kukjin Kim <kgene.kim@samsung.com>,
'Olof Johansson' <olof@lixom.net>,
linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org
Subject: Re: [GIT PULL] Samsung EXYNOS pm domains for devel
Date: Sun, 12 Feb 2012 02:57:00 +0900 [thread overview]
Message-ID: <4F36ABEC.6040409@samsung.com> (raw)
In-Reply-To: <201202111650.41617.arnd@arndb.de>
On 02/12/12 01:50, Arnd Bergmann wrote:
> On Friday 10 February 2012, Rafael J. Wysocki wrote:
>>> Rafael, do you want to keep the option of rebasing the patches that you
>>> got from Kukjin?
>>
>> No, I'm not going to rebase them.
>
> Ok, very good!
>
>>> If your workflow requires that, I can't take them, but
>>> if you can guarantee that the branch you have pulled them into is stable,
>>> I would prefer to pull it into a branch of arm-soc so that we can have
>>> other branches based on that where needed to avoid conflicts.
>>
>> OK, the relevant branch is linux-pm/pm-domains and it won't be rebased.
>> Please feel free to pull from it.
>
> Thanks,
Rafael, Arnd,
Thank you, too :)
Best regards,
Kgene.
--
Kukjin Kim <kgene.kim@samsung.com>, Senior Engineer,
SW Solution Development Team, Samsung Electronics Co., Ltd.
WARNING: multiple messages have this Message-ID (diff)
From: kgene.kim@samsung.com (Kukjin Kim)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] Samsung EXYNOS pm domains for devel
Date: Sun, 12 Feb 2012 02:57:00 +0900 [thread overview]
Message-ID: <4F36ABEC.6040409@samsung.com> (raw)
In-Reply-To: <201202111650.41617.arnd@arndb.de>
On 02/12/12 01:50, Arnd Bergmann wrote:
> On Friday 10 February 2012, Rafael J. Wysocki wrote:
>>> Rafael, do you want to keep the option of rebasing the patches that you
>>> got from Kukjin?
>>
>> No, I'm not going to rebase them.
>
> Ok, very good!
>
>>> If your workflow requires that, I can't take them, but
>>> if you can guarantee that the branch you have pulled them into is stable,
>>> I would prefer to pull it into a branch of arm-soc so that we can have
>>> other branches based on that where needed to avoid conflicts.
>>
>> OK, the relevant branch is linux-pm/pm-domains and it won't be rebased.
>> Please feel free to pull from it.
>
> Thanks,
Rafael, Arnd,
Thank you, too :)
Best regards,
Kgene.
--
Kukjin Kim <kgene.kim@samsung.com>, Senior Engineer,
SW Solution Development Team, Samsung Electronics Co., Ltd.
next prev parent reply other threads:[~2012-02-11 17:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-10 10:53 [GIT PULL] Samsung EXYNOS pm domains for devel Kukjin Kim
2012-02-10 10:53 ` Kukjin Kim
2012-02-10 22:05 ` Rafael J. Wysocki
2012-02-10 22:05 ` Rafael J. Wysocki
2012-02-10 23:34 ` Arnd Bergmann
2012-02-10 23:34 ` Arnd Bergmann
2012-02-10 23:42 ` Rafael J. Wysocki
2012-02-10 23:42 ` Rafael J. Wysocki
2012-02-11 16:50 ` Arnd Bergmann
2012-02-11 16:50 ` Arnd Bergmann
2012-02-11 17:57 ` Kukjin Kim [this message]
2012-02-11 17:57 ` Kukjin Kim
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=4F36ABEC.6040409@samsung.com \
--to=kgene.kim@samsung.com \
--cc=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=olof@lixom.net \
--cc=rjw@sisk.pl \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.