From: Santosh Shilimkar <santosh.shilimkar-l0cyMroinI0@public.gmane.org>
To: Grygorii Strashko <grygorii.strashko-l0cyMroinI0@public.gmane.org>
Cc: devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Subject: Re: [PATCH 0/4] ARM: dts: keystone: fixes
Date: Wed, 1 Oct 2014 09:54:33 -0400 [thread overview]
Message-ID: <542C0799.9020803@ti.com> (raw)
In-Reply-To: <1412159854-21143-1-git-send-email-grygorii.strashko-l0cyMroinI0@public.gmane.org>
On Wednesday 01 October 2014 06:37 AM, Grygorii Strashko wrote:
> Hi Snatosh,
>
> This small set of DTS fixes for Keystone 2 SoCs, which
> I've done while testing kernel boot on linux-next (3.18).
>
> Grygorii Strashko (4):
> ARM: dts: keystone: fix io range for usb_phy
> ARM: dts: keystone-k2e: update usb1 node for dma properties
> ARM: dts: keystone-k2e: fix mdio io start address
> ARM: dts: keystone-k2l: fix mdio io start address
>
Thanks Grygorii !!
I will queue this up for 3.18
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2014-10-01 13:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-01 10:37 [PATCH 0/4] ARM: dts: keystone: fixes Grygorii Strashko
[not found] ` <1412159854-21143-1-git-send-email-grygorii.strashko-l0cyMroinI0@public.gmane.org>
2014-10-01 10:37 ` [PATCH 1/4] ARM: dts: keystone: fix io range for usb_phy0 Grygorii Strashko
2014-10-01 10:37 ` [PATCH 2/4] ARM: dts: keystone-k2e: update usb1 node for dma properties Grygorii Strashko
2014-10-01 10:37 ` [PATCH 3/4] ARM: dts: keystone-k2e: fix mdio io start address Grygorii Strashko
2014-10-01 10:37 ` [PATCH 4/4] ARM: dts: keystone-k2l: " Grygorii Strashko
2014-10-01 13:54 ` 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=542C0799.9020803@ti.com \
--to=santosh.shilimkar-l0cymroini0@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=grygorii.strashko-l0cyMroinI0@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.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).