All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Vignesh R <vigneshr@ti.com>
Cc: Tero Kristo <t-kristo@ti.com>, Rob Herring <robh+dt@kernel.org>,
	Nishanth Menon <nm@ti.com>, Mark Rutland <mark.rutland@arm.com>,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
	linux-omap@vger.kernel.org,
	Linus Walleij <linus.walleij@linaro.org>
Subject: Re: [PATCH v2 1/4] dt-bindings: pinctrl: k3: Introduce pinmux definitions
Date: Sat, 17 Nov 2018 08:08:50 -0800	[thread overview]
Message-ID: <20181117160850.GN53235@atomide.com> (raw)
In-Reply-To: <20181113060111.16374-2-vigneshr@ti.com>

* Vignesh R <vigneshr@ti.com> [181113 06:00]:
> The dt-bindings header for TI K3 AM6 SoCs define a set of macros for
> defining pinmux configs in human readable form, instead of raw-coded
> hex values.

Looks good to me now too thanks:

Acked-by: Tony Lindgren <tony@atomide.com>

WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 1/4] dt-bindings: pinctrl: k3: Introduce pinmux definitions
Date: Sat, 17 Nov 2018 08:08:50 -0800	[thread overview]
Message-ID: <20181117160850.GN53235@atomide.com> (raw)
In-Reply-To: <20181113060111.16374-2-vigneshr@ti.com>

* Vignesh R <vigneshr@ti.com> [181113 06:00]:
> The dt-bindings header for TI K3 AM6 SoCs define a set of macros for
> defining pinmux configs in human readable form, instead of raw-coded
> hex values.

Looks good to me now too thanks:

Acked-by: Tony Lindgren <tony@atomide.com>

  parent reply	other threads:[~2018-11-17 16:08 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-13  6:01 [PATCH v2 0/4] AM654: Add pinmux support Vignesh R
2018-11-13  6:01 ` Vignesh R
2018-11-13  6:01 ` Vignesh R
2018-11-13  6:01 ` [PATCH v2 1/4] dt-bindings: pinctrl: k3: Introduce pinmux definitions Vignesh R
2018-11-13  6:01   ` Vignesh R
2018-11-13  6:01   ` Vignesh R
2018-11-17 12:27   ` Linus Walleij
2018-11-17 12:27     ` Linus Walleij
2018-11-17 15:43   ` Rob Herring
2018-11-17 15:43     ` Rob Herring
2018-11-17 15:43     ` Rob Herring
2018-11-17 16:05   ` Nishanth Menon
2018-11-17 16:05     ` Nishanth Menon
2018-11-17 16:05     ` Nishanth Menon
2018-11-19  7:19     ` Tero Kristo
2018-11-19  7:19       ` Tero Kristo
2018-11-19  7:19       ` Tero Kristo
2018-11-20 10:09       ` Vignesh R
2018-11-20 10:09         ` Vignesh R
2018-11-20 10:09         ` Vignesh R
2018-11-20 10:37         ` Tero Kristo
2018-11-20 10:37           ` Tero Kristo
2018-11-20 10:37           ` Tero Kristo
2018-11-20 10:44           ` Vignesh R
2018-11-20 10:44             ` Vignesh R
2018-11-20 10:44             ` Vignesh R
2018-11-23 10:21             ` Tero Kristo
2018-11-23 10:21               ` Tero Kristo
2018-11-23 10:21               ` Tero Kristo
2018-11-23 15:07               ` Nishanth Menon
2018-11-23 15:07                 ` Nishanth Menon
2018-11-23 15:07                 ` Nishanth Menon
2018-11-17 16:08   ` Tony Lindgren [this message]
2018-11-17 16:08     ` Tony Lindgren
2018-11-13  6:01 ` [PATCH v2 2/4] arm64: dts: ti: k3-am65: Add pinctrl regions Vignesh R
2018-11-13  6:01   ` Vignesh R
2018-11-13  6:01   ` Vignesh R
2018-11-13  6:01 ` [PATCH v2 3/4] arm64: dts: ti: am654-base-board: Add pinmux for main uart0 Vignesh R
2018-11-13  6:01   ` Vignesh R
2018-11-13  6:01   ` Vignesh R
2018-11-13  6:01 ` [PATCH v2 4/4] arm64: dts: ti: k3-am654-base-board: Add I2C nodes Vignesh R
2018-11-13  6:01   ` Vignesh R
2018-11-13  6:01   ` Vignesh R
2018-11-17 16:09   ` Nishanth Menon
2018-11-17 16:09     ` Nishanth Menon
2018-11-17 16:09     ` Nishanth Menon
2018-11-17 16:10 ` [PATCH v2 0/4] AM654: Add pinmux support Nishanth Menon
2018-11-17 16:10   ` Nishanth Menon
2018-11-17 16:10   ` Nishanth Menon

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=20181117160850.GN53235@atomide.com \
    --to=tony@atomide.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=nm@ti.com \
    --cc=robh+dt@kernel.org \
    --cc=t-kristo@ti.com \
    --cc=vigneshr@ti.com \
    /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.