From: Mike Turquette <mturquette@linaro.org>
To: Seungwon Jeon <essuuj@gmail.com>, Chris Ball <chris@printf.net>
Cc: Seungwon Jeon <tgih.jun@samsung.com>,
Zhangfei Gao <zhangfei.gao@linaro.org>,
Arnd Bergmann <arnd@arndb.de>,
Jaehoon Chung <jh80.chung@samsung.com>,
Haojian Zhuang <haojian.zhuang@linaro.org>,
brooke.wangzhigang@huawei.com, linux-mmc@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, patches@linaro.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH 2/2] mmc: dw_mmc: k3: remove clk_table
Date: Fri, 17 Jan 2014 14:56:31 -0800 [thread overview]
Message-ID: <20140117225631.4167.47840@quantum> (raw)
In-Reply-To: <CAFt19AB2Yk4U06-R9rMqFgEHFjN_L-pnc1wR35SQUjX28j7tZQ@mail.gmail.com>
Quoting Seungwon Jeon (2014-01-17 08:10:23)
> On Sat, Jan 18, 2014 at 12:01 AM, Chris Ball <chris@printf.net> wrote:
> >
> > Hi,
> >
> > On Tue, Jan 14 2014, Seungwon Jeon wrote:
> > > On Monday, January 13, 2014, Zhangfei Gao wrote:
> > >> Remove clk_table and directly use ios->clock as clock source rate.
> > >> Abstract init clock rate and max clock limitation in clk.c
> > >>
> > >> Signed-off-by: Zhangfei Gao <zhangfei.gao@linaro.org>
> > >
> > > Acked-by: Seungwon Jeon <tgih.jun@samsung.com>
> >
> > It looks like patch 1/2 did not make 3.14. Do you want me to take
> > this patch for 3.14 anyway? (Why?)
> Yes, I hope that it would be merged this time.
> I think that this change should have been applied to (036f29: mmc:
> dw_mmc: add dw_mmc-k3 for k3 platform) originally.
Oops, I just read this mail. I have taken in patch #1 through the clk
tree but have not yet pushed it out to my public mirror.
Chris, I'm happy to take it if you haven't yet.
Regards,
Mike
>
> Thanks,
> sw-j
next prev parent reply other threads:[~2014-01-17 22:56 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-13 9:14 [PATCH 0/2] mmc: dw_mmc: k3 remove clk_table Zhangfei Gao
2014-01-13 9:14 ` [PATCH 1/2] clk: hisilicon: add hi3620_mmc_clks Zhangfei Gao
2014-01-13 9:37 ` [PATCH] " Zhangfei Gao
2014-02-27 0:10 ` Mike Turquette
2014-01-14 9:47 ` [PATCH 1/2] " Seungwon Jeon
2014-01-14 10:04 ` Zhangfei Gao
2014-01-14 10:40 ` Seungwon Jeon
2014-01-14 11:52 ` zhangfei
[not found] ` <1389604469-8064-2-git-send-email-zhangfei.gao-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2014-01-14 20:17 ` Mike Turquette
2014-01-15 1:40 ` zhangfei
2014-01-15 3:53 ` Mike Turquette
2014-01-15 5:59 ` Haojian Zhuang
2014-01-15 8:29 ` Mike Turquette
2014-01-15 9:34 ` Haojian Zhuang
2014-01-15 16:14 ` Kevin Hilman
2014-01-13 9:14 ` [PATCH 2/2] mmc: dw_mmc: k3: remove clk_table Zhangfei Gao
2014-01-14 10:42 ` Seungwon Jeon
[not found] ` <002b01cf1115$4cdfe240$e69fa6c0$%jun-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2014-01-17 15:01 ` Chris Ball
2014-01-17 16:10 ` Seungwon Jeon
2014-01-17 22:56 ` Mike Turquette [this message]
2014-01-17 23:00 ` Chris Ball
2014-01-17 14:43 ` Seungwon Jeon
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=20140117225631.4167.47840@quantum \
--to=mturquette@linaro.org \
--cc=arnd@arndb.de \
--cc=brooke.wangzhigang@huawei.com \
--cc=chris@printf.net \
--cc=devicetree@vger.kernel.org \
--cc=essuuj@gmail.com \
--cc=haojian.zhuang@linaro.org \
--cc=jh80.chung@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mmc@vger.kernel.org \
--cc=patches@linaro.org \
--cc=tgih.jun@samsung.com \
--cc=zhangfei.gao@linaro.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).