From: Brian Norris <computersforpeace@gmail.com>
To: Brian Norris <briannorris@chromium.org>
Cc: Heiko Stuebner <heiko@sntech.de>,
linux-kernel@vger.kernel.org,
Doug Anderson <dianders@chromium.org>,
linux-rockchip@lists.infradead.org,
Nickey Yang <nickey.yang@rock-chips.com>,
mka@chromium.org, Chris Zhong <zyw@rock-chips.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] arm64: dts: rockchip: add rk3399 DSI0 reset
Date: Wed, 29 Nov 2017 17:10:05 -0800 [thread overview]
Message-ID: <20171130011005.GA124672@google.com> (raw)
In-Reply-To: <20171130010723.GA133459@google.com>
On Wed, Nov 29, 2017 at 05:07:27PM -0800, Brian Norris wrote:
Sorry, I got the wrong $subject, will resend :(
WARNING: multiple messages have this Message-ID (diff)
From: computersforpeace@gmail.com (Brian Norris)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm64: dts: rockchip: add rk3399 DSI0 reset
Date: Wed, 29 Nov 2017 17:10:05 -0800 [thread overview]
Message-ID: <20171130011005.GA124672@google.com> (raw)
In-Reply-To: <20171130010723.GA133459@google.com>
On Wed, Nov 29, 2017 at 05:07:27PM -0800, Brian Norris wrote:
Sorry, I got the wrong $subject, will resend :(
next prev parent reply other threads:[~2017-11-30 1:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-29 23:35 [PATCH] arm64: dts: rockchip: add rk3399 DSI0 reset Brian Norris
2017-11-29 23:35 ` Brian Norris
2017-11-29 23:35 ` Brian Norris
[not found] ` <20171129233541.51337-1-briannorris-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
2017-11-30 1:07 ` Brian Norris
2017-11-30 1:07 ` Brian Norris
2017-11-30 1:07 ` Brian Norris
2017-11-30 1:10 ` Brian Norris [this message]
2017-11-30 1:10 ` Brian Norris
2017-11-30 1:11 ` [PATCH] arm64: dts: rockchip: add mipi_dsi1 support for rk3399 Brian Norris
2017-11-30 1:11 ` Brian Norris
2017-12-04 10:01 ` Heiko Stuebner
2017-12-04 10:01 ` Heiko Stuebner
2017-12-04 9:58 ` [PATCH] arm64: dts: rockchip: add rk3399 DSI0 reset Heiko Stuebner
2017-12-04 9:58 ` 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=20171130011005.GA124672@google.com \
--to=computersforpeace@gmail.com \
--cc=briannorris@chromium.org \
--cc=dianders@chromium.org \
--cc=heiko@sntech.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=mka@chromium.org \
--cc=nickey.yang@rock-chips.com \
--cc=zyw@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.