From: Lee Jones <lee.jones@linaro.org>
To: Wadim Egorov <w.egorov@phytec.de>
Cc: Andy Yan <andy.yan@rock-chips.com>,
mark.rutland@arm.com, devicetree@vger.kernel.org,
a.zummo@towertech.it, pawel.moll@arm.com,
rtc-linux@googlegroups.com, ijc+devicetree@hellion.org.uk,
mturquette@baylibre.com, sboyd@codeaurora.org,
linux-kernel@vger.kernel.org, lgirdwood@gmail.com,
linux-rockchip@lists.infradead.org, robh+dt@kernel.org,
alexandre.belloni@free-electrons.com, broonie@kernel.org,
dianders@chromium.org, galak@codeaurora.org, zyw@rock-chips.com,
linux-clk@vger.kernel.org
Subject: Re: [RESEND PATCH v5 1/5] mfd: RK808: Add RK818 support
Date: Fri, 5 Aug 2016 13:22:01 +0100 [thread overview]
Message-ID: <20160805122201.GW5243@dell> (raw)
In-Reply-To: <577CBB62.8080806@phytec.de>
[...]
> Lee, you have already applied this series. But I can't find the patches
> in your kernel tree.
> I would like to read the device ID from the register in the probe function.
> Do you want me to base my changes on top of this series or send a new
> version?
Please rebase and resend the series.
--
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
prev parent reply other threads:[~2016-08-05 12:22 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-02 6:50 [RESEND PATCH v5 1/5] mfd: RK808: Add RK818 support Wadim Egorov
2016-06-02 6:50 ` [RESEND PATCH v5 2/5] regulator: rk808: Add regulator driver for RK818 Wadim Egorov
2016-06-02 6:50 ` [RESEND PATCH v5 3/5] mfd: dt-bindings: Add RK818 device tree bindings document Wadim Egorov
[not found] ` <1464850228-17244-3-git-send-email-w.egorov-guT5V/WYfQezQB+pC5nmwQ@public.gmane.org>
2016-06-08 14:23 ` Lee Jones
[not found] ` <1464850228-17244-1-git-send-email-w.egorov-guT5V/WYfQezQB+pC5nmwQ@public.gmane.org>
2016-06-02 6:50 ` [RESEND PATCH v5 4/5] clk: Kconfig: Name RK818 in Kconfig for COMMON_CLK_RK808 Wadim Egorov
[not found] ` <1464850228-17244-4-git-send-email-w.egorov-guT5V/WYfQezQB+pC5nmwQ@public.gmane.org>
2016-07-06 22:22 ` Michael Turquette
2016-06-02 6:50 ` [RESEND PATCH v5 5/5] rtc: Kconfig: Name RK818 in Kconfig for RTC_DRV_RK808 Wadim Egorov
2016-06-08 14:17 ` [RESEND PATCH v5 1/5] mfd: RK808: Add RK818 support Lee Jones
2016-06-09 8:23 ` Wadim Egorov
2016-06-09 11:12 ` Lee Jones
2016-06-09 13:11 ` Wadim Egorov
[not found] ` <57596B1C.2010101-guT5V/WYfQezQB+pC5nmwQ@public.gmane.org>
2016-06-09 15:28 ` Lee Jones
[not found] ` <5759277D.7090101-guT5V/WYfQezQB+pC5nmwQ@public.gmane.org>
2016-07-06 3:15 ` Andy Yan
[not found] ` <577C77DF.9060706-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2016-07-06 8:03 ` Wadim Egorov
[not found] ` <577CBB62.8080806-guT5V/WYfQezQB+pC5nmwQ@public.gmane.org>
2016-07-06 8:56 ` Andy Yan
2016-08-05 12:22 ` Lee Jones [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=20160805122201.GW5243@dell \
--to=lee.jones@linaro.org \
--cc=a.zummo@towertech.it \
--cc=alexandre.belloni@free-electrons.com \
--cc=andy.yan@rock-chips.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=lgirdwood@gmail.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=mturquette@baylibre.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=rtc-linux@googlegroups.com \
--cc=sboyd@codeaurora.org \
--cc=w.egorov@phytec.de \
--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 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).