From: "santosh.shilimkar@oracle.com" <santosh.shilimkar@oracle.com>
To: Olof Johansson <olof@lixom.net>
Cc: arm@kernel.org, linux-arm-kernel@lists.infradead.org,
khilman@kernel.org, arnd@arndb.de, linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL 1/3] ARM: Keystone DTS for 4.16
Date: Fri, 5 Jan 2018 10:45:57 -0800 [thread overview]
Message-ID: <2fcf4dfc-300b-afca-d093-ebd9c1779fcb@oracle.com> (raw)
In-Reply-To: <20180105071233.dlgob4hufvstuwi4@localhost>
On 1/4/18 11:12 PM, Olof Johansson wrote:
> On Wed, Dec 27, 2017 at 06:07:50PM -0800, Santosh Shilimkar wrote:
>> The following changes since commit 4fbd8d194f06c8a3fd2af1ce560ddb31f7ec8323:
>>
>> Linux 4.15-rc1 (2017-11-26 16:01:47 -0800)
>>
>> are available in the git repository at:
>>
>> git://git.kernel.org/pub/scm/linux/kernel/git/ssantosh/linux-keystone.git tags/keystone_dts_for_4.16
>>
>> for you to fetch changes up to 4fe85b0cdd06f8fef2631923799bdc95380badb5:
>>
>> ARM: dts: keystone-k2l-clocks: Add missing unit name to clock nodes that have regs (2017-12-16 14:36:57 -0800)
>>
>> ----------------------------------------------------------------
>> ARM: Keystone DTS update for 4.16
>>
>> - Enable GPIO bank2 for K2L
>> - Enable QSPI for K2G & K2G-EVM
>> - Enable UART1/2 for K2G & K2G-EVM
>> - Enable peripherals for K2G-ICE
>> - Fix C1 and C2 DTS warnings
>
> Merged, thanks.
>
Thanks !!
prev parent reply other threads:[~2018-01-05 18:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-28 2:07 [GIT PULL 1/3] ARM: Keystone DTS for 4.16 Santosh Shilimkar
2017-12-28 2:07 ` [GIT PULL 2/3] SOC: Keystone SOC update " Santosh Shilimkar
2018-01-05 7:13 ` Olof Johansson
2017-12-28 2:07 ` [GIT PULL 3/3] ARM: Keystone config " Santosh Shilimkar
2018-01-05 7:14 ` Olof Johansson
2018-01-05 7:12 ` [GIT PULL 1/3] ARM: Keystone DTS " Olof Johansson
2018-01-05 18:45 ` santosh.shilimkar [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=2fcf4dfc-300b-afca-d093-ebd9c1779fcb@oracle.com \
--to=santosh.shilimkar@oracle.com \
--cc=arm@kernel.org \
--cc=arnd@arndb.de \
--cc=khilman@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=olof@lixom.net \
/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