From: khilman@baylibre.com (Kevin Hilman)
To: linus-amlogic@lists.infradead.org
Subject: [RESEND PATCH 0/3] ARM64: dts: meson-gx: Cleanup for common nodes
Date: Thu, 23 Mar 2017 12:28:58 -0700 [thread overview]
Message-ID: <m2h92jlrlx.fsf@baylibre.com> (raw)
In-Reply-To: <1489396252-28696-1-git-send-email-narmstrong@baylibre.com> (Neil Armstrong's message of "Mon, 13 Mar 2017 10:10:49 +0100")
Neil Armstrong <narmstrong@baylibre.com> writes:
> Since we know the GXBB and GXL/GXM share more hardware, we can safely move
> the remaining peripheral nodes present in the GXBB dtsi to the common GX dtsi.
> The following patches are small cleanups and helps to uniform the GX common
> dtsi compatible scheme.
>
> Changes since original v1 at [1]:
> - Add back missing changelog on patches 1 and 3
Applied to v4.12/dt64,
Thanks,
Kevin
WARNING: multiple messages have this Message-ID (diff)
From: khilman@baylibre.com (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: [RESEND PATCH 0/3] ARM64: dts: meson-gx: Cleanup for common nodes
Date: Thu, 23 Mar 2017 12:28:58 -0700 [thread overview]
Message-ID: <m2h92jlrlx.fsf@baylibre.com> (raw)
In-Reply-To: <1489396252-28696-1-git-send-email-narmstrong@baylibre.com> (Neil Armstrong's message of "Mon, 13 Mar 2017 10:10:49 +0100")
Neil Armstrong <narmstrong@baylibre.com> writes:
> Since we know the GXBB and GXL/GXM share more hardware, we can safely move
> the remaining peripheral nodes present in the GXBB dtsi to the common GX dtsi.
> The following patches are small cleanups and helps to uniform the GX common
> dtsi compatible scheme.
>
> Changes since original v1 at [1]:
> - Add back missing changelog on patches 1 and 3
Applied to v4.12/dt64,
Thanks,
Kevin
WARNING: multiple messages have this Message-ID (diff)
From: Kevin Hilman <khilman-rdvid1DuHRBWk0Htik3J/w@public.gmane.org>
To: Neil Armstrong <narmstrong-rdvid1DuHRBWk0Htik3J/w@public.gmane.org>
Cc: carlo-KA+7E9HrN00dnm+yROfE0A@public.gmane.org,
linux-amlogic-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [RESEND PATCH 0/3] ARM64: dts: meson-gx: Cleanup for common nodes
Date: Thu, 23 Mar 2017 12:28:58 -0700 [thread overview]
Message-ID: <m2h92jlrlx.fsf@baylibre.com> (raw)
In-Reply-To: <1489396252-28696-1-git-send-email-narmstrong-rdvid1DuHRBWk0Htik3J/w@public.gmane.org> (Neil Armstrong's message of "Mon, 13 Mar 2017 10:10:49 +0100")
Neil Armstrong <narmstrong-rdvid1DuHRBWk0Htik3J/w@public.gmane.org> writes:
> Since we know the GXBB and GXL/GXM share more hardware, we can safely move
> the remaining peripheral nodes present in the GXBB dtsi to the common GX dtsi.
> The following patches are small cleanups and helps to uniform the GX common
> dtsi compatible scheme.
>
> Changes since original v1 at [1]:
> - Add back missing changelog on patches 1 and 3
Applied to v4.12/dt64,
Thanks,
Kevin
--
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
WARNING: multiple messages have this Message-ID (diff)
From: Kevin Hilman <khilman@baylibre.com>
To: Neil Armstrong <narmstrong@baylibre.com>
Cc: carlo@caione.org, linux-amlogic@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [RESEND PATCH 0/3] ARM64: dts: meson-gx: Cleanup for common nodes
Date: Thu, 23 Mar 2017 12:28:58 -0700 [thread overview]
Message-ID: <m2h92jlrlx.fsf@baylibre.com> (raw)
In-Reply-To: <1489396252-28696-1-git-send-email-narmstrong@baylibre.com> (Neil Armstrong's message of "Mon, 13 Mar 2017 10:10:49 +0100")
Neil Armstrong <narmstrong@baylibre.com> writes:
> Since we know the GXBB and GXL/GXM share more hardware, we can safely move
> the remaining peripheral nodes present in the GXBB dtsi to the common GX dtsi.
> The following patches are small cleanups and helps to uniform the GX common
> dtsi compatible scheme.
>
> Changes since original v1 at [1]:
> - Add back missing changelog on patches 1 and 3
Applied to v4.12/dt64,
Thanks,
Kevin
next prev parent reply other threads:[~2017-03-23 19:28 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-13 9:10 [RESEND PATCH 0/3] ARM64: dts: meson-gx: Cleanup for common nodes Neil Armstrong
2017-03-13 9:10 ` Neil Armstrong
2017-03-13 9:10 ` Neil Armstrong
2017-03-13 9:10 ` [RESEND PATCH 1/3] ARM64: dts: meson-gx: Finally move common nodes to GX dtsi Neil Armstrong
2017-03-13 9:10 ` Neil Armstrong
2017-03-13 9:10 ` Neil Armstrong
2017-03-13 9:10 ` Neil Armstrong
2017-03-13 9:10 ` [RESEND PATCH 2/3] ARM64: dts: meson-gx: empty line cleanup Neil Armstrong
2017-03-13 9:10 ` Neil Armstrong
2017-03-13 9:10 ` Neil Armstrong
2017-03-13 9:10 ` Neil Armstrong
2017-03-13 9:10 ` [RESEND PATCH 3/3] ARM64: dts: meson-gx: Prepend GX generic compatible like other nodes Neil Armstrong
2017-03-13 9:10 ` Neil Armstrong
2017-03-13 9:10 ` Neil Armstrong
2017-03-13 9:10 ` Neil Armstrong
2017-03-23 19:28 ` Kevin Hilman [this message]
2017-03-23 19:28 ` [RESEND PATCH 0/3] ARM64: dts: meson-gx: Cleanup for common nodes Kevin Hilman
2017-03-23 19:28 ` Kevin Hilman
2017-03-23 19:28 ` Kevin Hilman
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=m2h92jlrlx.fsf@baylibre.com \
--to=khilman@baylibre.com \
--cc=linus-amlogic@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.