From: santosh.shilimkar@ti.com (Santosh Shilimkar)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 1/3] ARM: keystone: device tree updates for 3.14
Date: Thu, 19 Dec 2013 19:03:52 -0500 [thread overview]
Message-ID: <52B38968.5070509@ti.com> (raw)
In-Reply-To: <8761qkjvf5.fsf@linaro.org>
Kevin,
On Thursday 19 December 2013 06:03 PM, Kevin Hilman wrote:
> Santosh Shilimkar <santosh.shilimkar@ti.com> writes:
>
>> Arnd, Olof, Kevin,
>>
>> Please pull below keystone device tree updates for 3.14
>>
>> Regards,
>> Santosh
>>
>> The following changes since commit 6ce4eac1f600b34f2f7f58f9cd8f0503d79e42ae:
>>
>> Linux 3.13-rc1 (2013-11-22 11:30:55 -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 you to fetch changes up to 732079567da4942b7b4929deff8f236926d0b3eb:
>>
>> ARM: dts: keystone: Add usb devicetree bindings (2013-12-12 20:29:17 -0500)
>>
>> ----------------------------------------------------------------
>> Keystone DTS updates for 3.14
>>
>> - ddr3 pll clock node typo fixup.
>> - EVM specific clock setting with board k2hk-evm.dts.
>> - GIC node updates for missing virtualisation info.
>> - Adding USB dwc3 and phy nodes.
>>
>> ----------------------------------------------------------------
>> Murali Karicheri (3):
>> ARM: keystone: dts: add a k2hk-evm specific dts file
>> ARM: keystone: dts: fix typo in the ddr3 pllclk node name
>> ARM: keystone: dts: add paclk divider clock node
>>
>> Santosh Shilimkar (2):
>> ARM: dts: keystone: Add the GICV and GICH address space
>> ARM: dts: keystone: Add guestos maintenance interrupt
>>
>> WingMan Kwok (2):
>> ARM: dts: keystone: Add usb phy devicetree bindings
>> ARM: dts: keystone: Add usb devicetree bindings
>
> I'm not willing to pull these new bindings.
>
> These new bindings don't have an ack from DT maintainers, and from a
> quick scan of the archives, don't appear to have ever been posted to the
> DT list. If they had been posted to the DT list, and hadn't had a
> response after 2 weeks, it would've been OK for you to queue them up for
> us, but as it stands they haven't even been posted for the attention of
> the DT maintainers. Please remedy that. Thanks.
>
Not sure if you got confused because of the subject line on couple
of patches. There are no new dt bindings in $subject pull request.
Its all just updating the machine dts files for existing bindings.
And hence explicitly not sent for device tree list.
I have some more dt patches which adds new bindings which has been
getting reviewed with dt folks. And since they are not yet acked,
i haven't included them in the series.
Can you please check one more time and let me know if I am missing
something ?
Regards,
Santosh
next prev parent reply other threads:[~2013-12-20 0:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-16 21:46 [GIT PULL 1/3] ARM: keystone: device tree updates for 3.14 Santosh Shilimkar
2013-12-16 21:46 ` [GIT PULL 2/3] ARM: keystone: SOC " Santosh Shilimkar
2013-12-19 23:10 ` Kevin Hilman
2013-12-20 0:41 ` Santosh Shilimkar
2013-12-16 21:46 ` [GIT PULL 3/3] ARM: MAINTAINERS: " Santosh Shilimkar
2013-12-19 23:14 ` Kevin Hilman
2013-12-20 0:46 ` Santosh Shilimkar
2013-12-19 23:03 ` [GIT PULL 1/3] ARM: keystone: device tree " Kevin Hilman
2013-12-20 0:03 ` Santosh Shilimkar [this message]
2013-12-20 15:51 ` Kevin Hilman
2013-12-20 16:16 ` Santosh Shilimkar
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=52B38968.5070509@ti.com \
--to=santosh.shilimkar@ti.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 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.