[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87963aff-148c-bbf5-9116-d2614f6991f4@oracle.com>
Date: Fri, 21 Apr 2017 14:50:12 -0700
From: Santosh Shilimkar <santosh.shilimkar@...cle.com>
To: "Rafael J. Wysocki" <rjw@...ysocki.net>
Cc: Arnd Bergmann <arnd@...db.de>,
Stephen Rothwell <sfr@...b.auug.org.au>,
Olof Johansson <olof@...om.net>,
ARM <linux-arm-kernel@...ts.infradead.org>,
Linux-Next Mailing List <linux-next@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Dave Gerlach <d-gerlach@...com>,
Santosh Shilimkar <ssantosh@...nel.org>,
Nishanth Menon <nm@...com>
Subject: Re: linux-next: manual merge of the pm tree with the arm-soc tree
On 4/21/2017 2:31 PM, Rafael J. Wysocki wrote:
> On Friday, April 21, 2017 02:02:35 PM santosh.shilimkar@...cle.com wrote:
>>
>> On 4/21/17 2:31 AM, Arnd Bergmann wrote:
>>> On Fri, Apr 21, 2017 at 8:39 AM, santosh.shilimkar@...cle.com
[...]
>>> I still see two conflicting trees in linux-next as of today, neither of
>>> them is your keystone tree:
>>>
>> In the list it was agreed that the patchset goes via arm-soc tree.
>
> OK, I missed that when I looked at it again a couple of days ago, sorry.
>
NP.
> I'll drop it from the pm-domains branch.
>
Thanks for clarification.
Regards,
Santosh
Powered by blists - more mailing lists