From: Tony Lindgren <tony-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
To: yegorslists-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org
Cc: linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH 0/3] Add additional OnRISC Baltos devices
Date: Tue, 26 Apr 2016 11:13:54 -0700 [thread overview]
Message-ID: <20160426181354.GN5995@atomide.com> (raw)
In-Reply-To: <1461675626-5818-1-git-send-email-yegorslists-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org>
* yegorslists-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org <yegorslists-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org> [160426 06:03]:
> From: Yegor Yefremov <yegorslists-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org>
>
> This series splits am335x-baltos.dtsi out of am335x-baltos-ir5221.dts to
> consolidate common configuration for Baltos device.
>
> DTS files for Baltos IR3220 and IR2110 will be added using newly created
> am335x-baltos.dtsi.
Thanks applying into omap-for-v4.7/dt.
Tony
--
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:[~2016-04-26 18:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-26 13:00 [PATCH 0/3] Add additional OnRISC Baltos devices yegorslists-gM/Ye1E23mwN+BqQ9rBEUg
[not found] ` <1461675626-5818-1-git-send-email-yegorslists-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org>
2016-04-26 13:00 ` [PATCH 1/3] ARM: dts: split am335x-baltos-ir5221 into dts and dtsi files yegorslists-gM/Ye1E23mwN+BqQ9rBEUg
2016-04-26 13:00 ` [PATCH 2/3] ARM: dts: add DTS for Baltos IR3220 yegorslists-gM/Ye1E23mwN+BqQ9rBEUg
2016-04-26 13:00 ` [PATCH 3/3] ARM: dts: add DTS for Baltos IR2110 yegorslists-gM/Ye1E23mwN+BqQ9rBEUg
2016-04-26 18:13 ` Tony Lindgren [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=20160426181354.GN5995@atomide.com \
--to=tony-4v6ys6ai5vpbdgjk7y7tuq@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=yegorslists-gM/Ye1E23mwN+BqQ9rBEUg@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).