From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Paul Gortmaker <paul.gortmaker@windriver.com>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
Chen Gang <xili_gchen_5257@hotmail.com>,
Greg KH <gregkh@linuxfoundation.org>,
Simon Horman <horms+renesas@verge.net.au>, <cj@linux.com>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Jesper Nilsson <jesper.nilsson@axis.com>,
Mikael Starvik <starvik@axis.com>,
driverdevel <devel@driverdev.osuosl.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] staging: board: Kconfig: Let STAGING_BOARD depend on CLKDEV_LOOKUP
Date: Tue, 7 Jul 2015 00:44:29 +1000 [thread overview]
Message-ID: <20150707004429.51c92582@canb.auug.org.au> (raw)
In-Reply-To: <20150706134247.GD11898@windriver.com>
[-- Attachment #1: Type: text/plain, Size: 1909 bytes --]
Hi Paul,
On Mon, 6 Jul 2015 09:42:47 -0400 Paul Gortmaker <paul.gortmaker@windriver.com> wrote:
>
> [Re: [PATCH] staging: board: Kconfig: Let STAGING_BOARD depend on CLKDEV_LOOKUP] On 06/07/2015 (Mon 08:48) Stephen Rothwell wrote:
>
> > On Sun, 5 Jul 2015 18:57:51 +0200 Geert Uytterhoeven <geert@linux-m68k.org> wrote:
> > >
> > > On Sat, Jul 4, 2015 at 11:35 PM, Chen Gang <xili_gchen_5257@hotmail.com> wrote:
> > > > It needs clk_add_alias() from clk drivers, which is implemented in
> > > > "drivers/clk/clkdev.c" which depends on CLKDEV_LOOKUP.
> > > >
> > > > Normally, archs and clk driver its own will decide whether select
> > > > CLKDEV_LOOKUP, and common drivers will decide whether depend on it.
> > > >
> > > > The related error (with allmodconfig under cris for next-20150702):
> > > >
> > > > drivers/built-in.o: In function `board_staging_register_clock':
> > > > drivers/staging/board/board.c:131: undefined reference to `clk_add_alias'
> > > >
> > > >
> > > > Signed-off-by: Chen Gang <gang.chen.5i5j@gmail.com>
> > >
> > > Fix available for the last 15 days:
> > >
> > > https://lkml.org/lkml/2015/6/20/215
> >
> > I added Chen's patch to my fixes tree today (only because I couldn't
> > easily find a copy of Paul's patch (sorry Paul) i.e. how does one get a
> > full mail message from lkml.org? Or Geert, maybe that is not the best
> > place to link to.
>
> I have had reasonable success pulling stuff out of lkml patchworks:
>
> https://patchwork.kernel.org/patch/6651831/
>
> BTW, Chen's patch is missing the OF_IRQ dependency Geert found in
> his build coverage; I'd folded that into the v2 above, figuring
> that is what he'd desired I do with it.
I have replaced Chen's patch with your patch in my fixes tree ...
hopefully it won;t need to be there long.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2015-07-06 14:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-04 21:35 Chen Gang
2015-07-05 16:57 ` Geert Uytterhoeven
2015-07-05 22:48 ` Stephen Rothwell
2015-07-06 2:32 ` Chen Gang
2015-07-06 13:42 ` Paul Gortmaker
2015-07-06 13:58 ` Geert Uytterhoeven
2015-07-06 14:44 ` Stephen Rothwell [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=20150707004429.51c92582@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=cj@linux.com \
--cc=devel@driverdev.osuosl.org \
--cc=geert+renesas@glider.be \
--cc=geert@linux-m68k.org \
--cc=gregkh@linuxfoundation.org \
--cc=horms+renesas@verge.net.au \
--cc=jesper.nilsson@axis.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paul.gortmaker@windriver.com \
--cc=starvik@axis.com \
--cc=xili_gchen_5257@hotmail.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
all inboxes | Powered by JetHome®