devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Lothar Waßmann" <LW@KARO-electronics.de>
To: "Anson Huang" <b20788@freescale.com>,
	"Bai Ping" <b51503@freescale.com>,
	"Frank Li" <Frank.Li@freescale.com>,
	"Fugang Duan" <B38611@freescale.com>,
	"Ian Campbell" <ijc+devicetree@hellion.org.uk>,
	"Kumar Gala" <galak@codeaurora.org>,
	"Lothar Waßmann" <LW@KARO-electronics.de>,
	"Mark Rutland" <mark.rutland@arm.com>,
	"Michael Turquette" <mturquette@baylibre.com>,
	"Pawel Moll" <pawel.moll@arm.com>,
	"Rob Herring" <robh+dt@kernel.org>,
	"Russell King" <linux@arm.linux.org.uk>,
	"Sascha Hauer" <kernel@pengutronix.de>,
	"Shawn Guo" <shawnguo@kernel.org>,
	"Stephen Boyd" <sboyd@codeaurora.org>,
	devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/2] cleanup and add missing input_sel settings to imx6ul-pinfunc.h
Date: Fri, 26 Feb 2016 15:52:57 +0100	[thread overview]
Message-ID: <1456498379-6109-1-git-send-email-LW@KARO-electronics.de> (raw)
In-Reply-To: 20160226124413.71cef89a@ipc1.ka-ro

This patchset adds missing input_sel settings to imx6ul-pinfunc.h.
The first patch is a cleanup patch with no functional changes
intended.

       reply	other threads:[~2016-02-26 14:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20160226124413.71cef89a@ipc1.ka-ro>
2016-02-26 14:52 ` Lothar Waßmann [this message]
2016-02-26 14:52   ` [PATCH 1/2] ARM: dts: imx6ul: whitespace cleanup; no functional change Lothar Waßmann
2016-02-26 14:52   ` [PATCH 2/2] ARM: dts: imx6ul: add missing input_sel config for various pins Lothar Waßmann
2016-02-28  3:08   ` [PATCH 0/2] cleanup and add missing input_sel settings to imx6ul-pinfunc.h Shawn Guo

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=1456498379-6109-1-git-send-email-LW@KARO-electronics.de \
    --to=lw@karo-electronics.de \
    --cc=B38611@freescale.com \
    --cc=Frank.Li@freescale.com \
    --cc=b20788@freescale.com \
    --cc=b51503@freescale.com \
    --cc=devicetree@vger.kernel.org \
    --cc=galak@codeaurora.org \
    --cc=ijc+devicetree@hellion.org.uk \
    --cc=kernel@pengutronix.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=mark.rutland@arm.com \
    --cc=mturquette@baylibre.com \
    --cc=pawel.moll@arm.com \
    --cc=robh+dt@kernel.org \
    --cc=sboyd@codeaurora.org \
    --cc=shawnguo@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 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).