From: Tony Lindgren <tony@atomide.com>
To: Christina Quast <cquast@hanoverdisplays.com>
Cc: Benoit Cousson <bcousson@baylibre.com>,
Mark Jackson <mpfj@newflow.co.uk>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Russell King <linux@armlinux.org.uk>,
linux-omap@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 00/17] ARM: dts: am335x: Replace numeric pinmux address w. macro for remaining boards
Date: Mon, 15 Apr 2019 08:27:50 -0700 [thread overview]
Message-ID: <20190415152750.GB2839@atomide.com> (raw)
In-Reply-To: <20190412162627.24518-1-cquast@hanoverdisplays.com>
* Christina Quast <cquast@hanoverdisplays.com> [190412 09:27]:
> Last patch set of the patch series for the remaining 17 boards.
Thanks applying into omap-for-v5.2/dt-am3.
Regards,
Tony
prev parent reply other threads:[~2019-04-15 15:27 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-12 16:26 [PATCH 00/17] ARM: dts: am335x: Replace numeric pinmux address w. macro for remaining boards Christina Quast
2019-04-12 16:26 ` Christina Quast
2019-04-12 16:26 ` [PATCH 01/17] ARM: dts: am335x: igep0033: Replaced register offsets with defines Christina Quast
2019-04-12 16:26 ` Christina Quast
2019-04-12 16:26 ` [PATCH 02/17] ARM: dts: am335x: lxm: " Christina Quast
2019-04-12 16:26 ` Christina Quast
2019-04-12 16:26 ` [PATCH 03/17] ARM: dts: am335x: moxa-uc-2100-common: " Christina Quast
2019-04-12 16:26 ` Christina Quast
2019-04-12 16:26 ` [PATCH 04/17] ARM: dts: am335x: moxa-uc-2101: " Christina Quast
2019-04-12 16:26 ` Christina Quast
2019-04-12 16:26 ` [PATCH 05/17] ARM: dts: am335x: moxa-uc-8100-me-t: " Christina Quast
2019-04-12 16:26 ` Christina Quast
2019-04-12 16:26 ` [PATCH 06/17] ARM: dts: am335x: nano: " Christina Quast
2019-04-12 16:26 ` Christina Quast
2019-04-12 16:26 ` [PATCH 07/17] ARM: dts: am335x: osd3358-sm-red: " Christina Quast
2019-04-12 16:26 ` Christina Quast
2019-04-12 16:26 ` [PATCH 08/17] ARM: dts: am335x: osd335x-common: " Christina Quast
2019-04-12 16:26 ` Christina Quast
2019-04-12 16:26 ` [PATCH 09/17] ARM: dts: am335x: pcm-953: " Christina Quast
2019-04-12 16:26 ` Christina Quast
2019-04-12 16:26 ` [PATCH 10/17] ARM: dts: am335x: pdu001: " Christina Quast
2019-04-12 16:26 ` Christina Quast
2019-04-12 16:26 ` [PATCH 11/17] ARM: dts: am335x: pepper: " Christina Quast
2019-04-12 16:26 ` Christina Quast
2019-04-12 16:26 ` [PATCH 12/17] ARM: dts: am335x: phycore-som: " Christina Quast
2019-04-12 16:26 ` Christina Quast
2019-04-12 16:26 ` [PATCH 13/17] ARM: dts: am335x: sancloud-bbe: " Christina Quast
2019-04-12 16:26 ` Christina Quast
2019-04-12 16:26 ` [PATCH 14/17] ARM: dts: am335x: sbc-t335: " Christina Quast
2019-04-12 16:26 ` Christina Quast
2019-04-12 16:26 ` [PATCH 15/17] ARM: dts: am335x: shc: " Christina Quast
2019-04-12 16:26 ` Christina Quast
2019-04-12 16:26 ` [PATCH 16/17] ARM: dts: am335x: sl50: " Christina Quast
2019-04-12 16:26 ` Christina Quast
2019-04-12 16:26 ` [PATCH 17/17] ARM: dts: am335x: wega: " Christina Quast
2019-04-12 16:26 ` Christina Quast
2019-04-15 15:27 ` 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=20190415152750.GB2839@atomide.com \
--to=tony@atomide.com \
--cc=bcousson@baylibre.com \
--cc=cquast@hanoverdisplays.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mark.rutland@arm.com \
--cc=mpfj@newflow.co.uk \
--cc=robh+dt@kernel.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.