All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Bolle <pebolle@tiscali.nl>
To: Haojian Zhuang <haojian.zhuang@linaro.org>
Cc: Mike Turquette <mturquette@linaro.org>,
	Zhangfei Gao <zhangfei.gao@linaro.org>,
	Haifeng Yan <haifeng.yan@linaro.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: clk: hisilicon: ARCH_HIP04 and ARCH_HIX5HD2?
Date: Fri, 05 Sep 2014 01:07:08 +0200	[thread overview]
Message-ID: <1409872027.5546.132.camel@x220> (raw)
In-Reply-To: <CAD6h2NRb3tStSy-qiBRQHDo7Yy=Obvgt1hx17M13atXEtTxcaA@mail.gmail.com>

On Thu, 2014-06-19 at 17:00 +0800, Haojian Zhuang wrote:
> On 19 June 2014 16:50, Paul Bolle <pebolle@tiscali.nl> wrote:
> > 0) Commit d3e6573c48f4 ("clk: hip04: add clock driver") was included in
> > v3.15. That clock driver is built only if CONFIG_ARCH_HIP04 is set.
> >
> > And commit 5efaf09021a5 ("clk: hisi: add clk-hix5hd2.c") was included in
> > v3.16-rc1. And that driver is built only if CONFIG_ARCH_HIX5HD2 is set.
> >
> > 1) Neither the symbol ARCH_HIP04 nor the symbol ARCH_HIX5HD2 is part of
> > v3.16-rc1. These symbols are also not part of next-20140619. I assume
> > that both are pending somewhere. Is that correct?
> >
> > 2) It would probably be nice if these drivers got some (automatic) build
> > coverage until those symbols enter the tree. I don't know how that could
> > be achieved.
> 
> Because clock driver is the first component should be merged into
> kernel tree. Otherwise, SoC couldn't be compiled at all since SoC &
> clock are in two different git tree.
> 
> I also hope that SoC patches could be merged as soon as possible. But
> we also need to follow up the comments on SoC patches from mailing
> list. I can't not say when those SoC patches could be merged into
> mainline since I'm not the gate keeper. I could only say that we're
> making effort on this.

ARCH_HIX5HD2 landed in v3.17-rc1, so it left my list of minor worries.

I assume the code to add ARCH_HIP04 is still being worked on. Is that
correct?


Paul Bolle


  reply	other threads:[~2014-09-04 23:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-19  8:50 clk: hisilicon: ARCH_HIP04 and ARCH_HIX5HD2? Paul Bolle
2014-06-19  9:00 ` Haojian Zhuang
2014-09-04 23:07   ` Paul Bolle [this message]
2014-09-14 16:47     ` Haojian Zhuang

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=1409872027.5546.132.camel@x220 \
    --to=pebolle@tiscali.nl \
    --cc=haifeng.yan@linaro.org \
    --cc=haojian.zhuang@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mturquette@linaro.org \
    --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 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.