Linux-Next Archive on lore.kernel.org
 help / color / Atom feed
From: Maxime Ripard <maxime@cerno.tech>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Mike Turquette <mturquette@baylibre.com>,
	Stephen Boyd <sboyd@kernel.org>,
	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: Tue, 30 Jun 2020 10:11:15 +0200
Message-ID: <20200630081115.mmqdsm3vlnj4yagu@gilmour.lan> (raw)
In-Reply-To: <20200630095341.0f4ae8ed@canb.auug.org.au>


[-- Attachment #1: Type: text/plain, Size: 588 bytes --]

Hi,

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?

Maxime

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  reply index

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-29 23:53 Stephen Rothwell
2020-06-30  8:11 ` Maxime Ripard [this message]
2020-07-08 11:10   ` Stephen Rothwell
  -- 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=20200630081115.mmqdsm3vlnj4yagu@gilmour.lan \
    --to=maxime@cerno.tech \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mturquette@baylibre.com \
    --cc=sboyd@kernel.org \
    --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

Linux-Next Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/linux-next/0 linux-next/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-next linux-next/ https://lore.kernel.org/linux-next \
		linux-next@vger.kernel.org
	public-inbox-index linux-next

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.linux-next


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git