From: "Rafał Miłecki" <rafal@milecki.pl>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Richard Weinberger <richard.weinberger@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build failure after merge of the mtd tree
Date: Mon, 15 Feb 2021 09:55:49 +0100 [thread overview]
Message-ID: <b5b62cbc-88a3-c865-d3be-8a86018d822c@milecki.pl> (raw)
In-Reply-To: <20210215122854.4103ef4d@canb.auug.org.au>
Hi Stephen!
On 15.02.2021 02:28, Stephen Rothwell wrote:
> After merging the mtd tree, today's linux-next build (x86_64 allmodconfig)
> failed like this:
>
> ERROR: modpost: missing MODULE_LICENSE() in drivers/mtd/parsers/bcm4908-partitions.o
> ERROR: modpost: "bcm4908_partitions_post_parse" [drivers/mtd/parsers/ofpart.ko] undefined!
>
> Caused by commit
>
> 09cf6ee6d21c ("mtd: parsers: ofpart: support BCM4908 fixed partitions")
>
> I have used the mtd tree from next-20210212 for today.
Thank you for the report!
It has been fixed by the
[PATCH] mtd: parsers: ofpart: fix building as module
https://patchwork.ozlabs.org/project/linux-mtd/patch/20210215072844.16136-1-zajec5@gmail.com/
https://git.kernel.org/pub/scm/linux/kernel/git/mtd/linux.git/commit/?h=mtd/next&id=bc6dcf44da2bea215ae3edbdac5d350e96de3996
next prev parent reply other threads:[~2021-02-15 12:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-15 1:28 linux-next: build failure after merge of the mtd tree Stephen Rothwell
2021-02-15 8:55 ` Rafał Miłecki [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-04-08 1:42 Stephen Rothwell
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=b5b62cbc-88a3-c865-d3be-8a86018d822c@milecki.pl \
--to=rafal@milecki.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=richard.weinberger@gmail.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 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.