From: Randy Dunlap <rdunlap@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
Danil Kipnis <danil.kipnis@cloud.ionos.com>,
Jack Wang <jinpu.wang@cloud.ionos.com>
Subject: Re: linux-next: Tree for May 19 (block/rnbd/)
Date: Tue, 19 May 2020 11:59:48 -0700 [thread overview]
Message-ID: <86962843-e786-4a3f-0b85-1e06fbdbd76a@infradead.org> (raw)
In-Reply-To: <20200520040354.3e619918@canb.auug.org.au>
On 5/19/20 11:03 AM, Stephen Rothwell wrote:
> Hi all,
>
> News: there will be no linux-next release tomorrow.
>
> Changes since 20200518:
>
seen on i386:
when CONFIG_MODULES is not set/enabled:
../drivers/block/rnbd/rnbd-clt-sysfs.c: In function 'rnbd_clt_remove_dev_symlink':
../drivers/block/rnbd/rnbd-clt-sysfs.c:435:39: error: implicit declaration of function 'module_is_live'; did you mean 'module_driver'? [-Werror=implicit-function-declaration]
if (strlen(dev->blk_symlink_name) && module_is_live(THIS_MODULE))
^~~~~~~~~~~~~~
module_driver
--
~Randy
Reported-by: Randy Dunlap <rdunlap@infradead.org>
next parent reply other threads:[~2020-05-19 18:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200520040354.3e619918@canb.auug.org.au>
2020-05-19 18:59 ` Randy Dunlap [this message]
2020-05-20 10:12 ` linux-next: Tree for May 19 (block/rnbd/) Danil Kipnis
2020-05-21 17:50 ` [PATCH] rnbd: fix compilation error when CONFIG_MODULES is disabled Danil Kipnis
2020-05-21 18:39 ` Randy Dunlap
2020-05-21 18:59 ` Danil Kipnis
2020-05-23 0:24 ` Jason Gunthorpe
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=86962843-e786-4a3f-0b85-1e06fbdbd76a@infradead.org \
--to=rdunlap@infradead.org \
--cc=danil.kipnis@cloud.ionos.com \
--cc=jinpu.wang@cloud.ionos.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.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
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).