All of lore.kernel.org
 help / color / mirror / Atom feed
From: Heiko Stuebner <heiko@sntech.de>
To: Sugar Zhang <sugar.zhang@rock-chips.com>
Cc: broonie@kernel.org, linux-rockchip@lists.infradead.org,
	Rob Herring <robh+dt@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Russell King <linux@armlinux.org.uk>,
	linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ARM: dts: rk322x: fix i2s1 pinctrl error
Date: Fri, 09 Jun 2017 12:56:04 +0200	[thread overview]
Message-ID: <1870239.lCo0kzT3Kb@phil> (raw)
In-Reply-To: <1496998967-31520-1-git-send-email-sugar.zhang@rock-chips.com>

Hi,

Am Freitag, 9. Juni 2017, 17:02:47 CEST schrieb Sugar Zhang:
> Signed-off-by: Sugar Zhang <sugar.zhang@rock-chips.com>

I've already applied a previous version (from you and Frank).
See
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/arch/arm/boot/dts/rk322x.dtsi?id=9d420e9b4140f8938ad6aa0d29e2428a2af6122b


Heiko

WARNING: multiple messages have this Message-ID (diff)
From: heiko@sntech.de (Heiko Stuebner)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: dts: rk322x: fix i2s1 pinctrl error
Date: Fri, 09 Jun 2017 12:56:04 +0200	[thread overview]
Message-ID: <1870239.lCo0kzT3Kb@phil> (raw)
In-Reply-To: <1496998967-31520-1-git-send-email-sugar.zhang@rock-chips.com>

Hi,

Am Freitag, 9. Juni 2017, 17:02:47 CEST schrieb Sugar Zhang:
> Signed-off-by: Sugar Zhang <sugar.zhang@rock-chips.com>

I've already applied a previous version (from you and Frank).
See
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/arch/arm/boot/dts/rk322x.dtsi?id=9d420e9b4140f8938ad6aa0d29e2428a2af6122b


Heiko

  reply	other threads:[~2017-06-09 10:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-09  9:02 [PATCH] ARM: dts: rk322x: fix i2s1 pinctrl error Sugar Zhang
2017-06-09  9:02 ` Sugar Zhang
2017-06-09 10:56 ` Heiko Stuebner [this message]
2017-06-09 10:56   ` Heiko Stuebner

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=1870239.lCo0kzT3Kb@phil \
    --to=heiko@sntech.de \
    --cc=broonie@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=linux@armlinux.org.uk \
    --cc=mark.rutland@arm.com \
    --cc=robh+dt@kernel.org \
    --cc=sugar.zhang@rock-chips.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.