From: Stephen Boyd <sboyd@kernel.org>
To: Mike Turquette <mturquette@baylibre.com>,
Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Maxime Ripard <maxime@cerno.tech>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: build warning after merge of the clk tree
Date: Wed, 15 Jul 2020 17:25:38 -0700 [thread overview]
Message-ID: <159485913896.1987609.15038060066931263381@swboyd.mtv.corp.google.com> (raw)
In-Reply-To: <20200708211044.3032905d@canb.auug.org.au>
Quoting Stephen Rothwell (2020-07-08 04:10:44)
> Hi all,
>
> On Tue, 30 Jun 2020 10:11:15 +0200 Maxime Ripard <maxime@cerno.tech> wrote:
> >
> > On Tue, Jun 30, 2020 at 09:53:41AM +1000, Stephen Rothwell wrote:
> > > After merging the clk tree, today's linux-next build (x86_64 allmodconfig)
> > > produced this warning:
> > >
> > > WARNING: modpost: missing MODULE_LICENSE() in drivers/clk/bcm/clk-bcm2711-dvp.o
> > >
> > > Introduced by commit
> > >
> > > 1bc95972715a ("clk: bcm: Add BCM2711 DVP driver")
> >
> > I've posted a patch solving this already:
> > https://lore.kernel.org/linux-clk/20200626112513.90816-1-maxime@cerno.tech/
> >
> > And it's supposed to be in clk-next since friday, but it looks like
> > stephen didn't push his branch?
>
> I am still getting this warning.
>
Sorry I forgot to push it out. Should be fixed now.
next prev parent reply other threads:[~2020-07-16 0:25 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-29 23:53 linux-next: build warning after merge of the clk tree Stephen Rothwell
2020-06-30 8:11 ` Maxime Ripard
2020-07-08 11:10 ` Stephen Rothwell
2020-07-16 0:25 ` Stephen Boyd [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-08-15 23:57 Stephen Rothwell
2019-08-16 18:10 ` Stephen Boyd
2019-04-30 0:19 Stephen Rothwell
2019-04-30 1:44 ` Anson Huang
2019-04-30 5:56 ` Stephen Rothwell
2018-10-17 21:51 Stephen Rothwell
2018-10-18 18:21 ` Stephen Boyd
2016-12-11 21:39 Stephen Rothwell
2016-12-12 8:05 ` Boris Brezillon
2016-12-12 8:19 ` Stephen Rothwell
2015-05-06 4:05 Stephen Rothwell
2015-05-06 4:41 ` Stephen Boyd
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=159485913896.1987609.15038060066931263381@swboyd.mtv.corp.google.com \
--to=sboyd@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=maxime@cerno.tech \
--cc=mturquette@baylibre.com \
--cc=sfr@canb.auug.org.au \
/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).