From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Randy Dunlap <rdunlap@infradead•org>
Cc: Linux Next Mailing List <linux-next@vger•kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Brendan Higgins <brendanhiggins@google•com>,
linux-kselftest@vger•kernel.org,
Shuah Khan <skhan@linuxfoundation•org>,
"Rafael J. Wysocki" <rjw@rjwysocki•net>,
Dmitry Torokhov <dmitry.torokhov@gmail•com>,
Alan Maguire <alan.maguire@oracle•com>
Subject: Re: linux-next: Tree for Jan 13 (drivers/base/test/property-entry-test.o)
Date: Tue, 14 Jan 2020 10:40:49 +1100 [thread overview]
Message-ID: <20200114104049.5244f612@canb.auug.org.au> (raw)
In-Reply-To: <eddaa93c-3bde-a9ed-5ee7-766f3cd51a43@infradead.org>
[-- Attachment #1: Type: text/plain, Size: 554 bytes --]
Hi Randy,
On Mon, 13 Jan 2020 14:59:54 -0800 Randy Dunlap <rdunlap@infradead•org> wrote:
>
> on i386:
>
> WARNING: modpost: missing MODULE_LICENSE() in drivers/base/test/property-entry-test.o
> see include/linux/module.h for more information
Sorry, I missed that yesterday.
Caused by commit
c032ace71c29 ("software node: add basic tests for property entries")
from the pm tree interacting with commit
9fe124bf1b77 ("kunit: allow kunit to be loaded as a module")
from the kunit-next tree.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-01-13 23:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-13 7:14 linux-next: Tree for Jan 13 Stephen Rothwell
2020-01-13 18:27 ` BUG_ON hit in "reimplement path_mountpoint() with less magic" [Was: Re: linux-next: Tree for Jan 13] Jason A. Donenfeld
2020-01-13 19:23 ` Al Viro
2020-01-13 19:33 ` Jason A. Donenfeld
2020-01-13 22:59 ` linux-next: Tree for Jan 13 (drivers/base/test/property-entry-test.o) Randy Dunlap
2020-01-13 23:40 ` Stephen Rothwell [this message]
2020-01-14 1:10 ` Brendan Higgins
2020-01-14 16:14 ` Alan Maguire
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=20200114104049.5244f612@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=alan.maguire@oracle$(echo .)com \
--cc=brendanhiggins@google$(echo .)com \
--cc=dmitry.torokhov@gmail$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-kselftest@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=rdunlap@infradead$(echo .)org \
--cc=rjw@rjwysocki$(echo .)net \
--cc=skhan@linuxfoundation$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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