From: Fengguang Wu <lkp@intel•com>
To: Oleg Nesterov <oleg@redhat•com>
Cc: Stephen Rothwell <sfr@canb•auug.org.au>,
linux-kernel@vger•kernel.org, Jens Axboe <axboe@fb•com>,
linux-next@vger•kernel.org, kbuild-all@01•org,
Markus Pargmann <mpa@pengutronix•de>,
Andrew Morton <akpm@linux-foundation•org>
Subject: Re: [kbuild-all] linux-next: build failure after merge of the akpm-current tree
Date: Mon, 2 Nov 2015 10:43:09 +0800 [thread overview]
Message-ID: <20151102024309.GA7966@wfg-t540p.sh.intel.com> (raw)
In-Reply-To: <20151101183754.GB32642@redhat.com>
On Sun, Nov 01, 2015 at 07:37:55PM +0100, Oleg Nesterov wrote:
> On 11/02, kbuild test robot wrote:
> >
> > Hi Stephen,
> >
> > [auto build test ERROR on v4.3-rc7 -- if it's inappropriate base, please suggest rules for selecting the more suitable base]
> >
> > url: https://github.com/0day-ci/linux/commits/Stephen-Rothwell/linux-next-build-failure-after-merge-of-the-akpm-current-tree/20151102-001657
> > config: i386-randconfig-x004-11010709 (attached as .config)
> > reproduce:
> > # save the attached .config to linux build tree
> > make ARCH=i386
> >
> > All errors (new ones prefixed by >>):
> >
> > drivers/block/nbd.c: In function 'nbd_thread_send':
> > >> drivers/block/nbd.c:596:3: error: implicit declaration of function 'kernel_dequeue_signal' [-Werror=implicit-function-declaration]
> > kernel_dequeue_signal(NULL);
> > ^
> > cc1: some warnings being treated as errors
> >
> > vim +/kernel_dequeue_signal +596 drivers/block/nbd.c
> >
> > 590 spin_lock_irqsave(&nbd->tasks_lock, flags);
> > 591 nbd->task_send = NULL;
> > 592 spin_unlock_irqrestore(&nbd->tasks_lock, flags);
> > 593
> > 594 /* Clear maybe pending signals */
> > 595 if (signal_pending(current))
> > > 596 kernel_dequeue_signal(NULL);
> > 597
> > 598 return 0;
> > 599 }
>
> Yes, de90fc653be60b4cec1a4d40f0e82164ec79f077 ("linux-next: build failure
> after merge of the akpm-current tree") should be applied on top of -mm.
Yes, sorry for the noise! I'll skip testing Stephen's linux-next fixup
patches. It turns out to be time sensitive: the robot might see the
build fix patch in mailing list before see the updated linux-next git
tree, which makes git-am to linux-next failed and fallback to git-am
to RC release.
Thanks,
Fengguang
next prev parent reply other threads:[~2015-11-02 2:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-01 16:15 linux-next: build failure after merge of the akpm-current tree Stephen Rothwell
2015-11-01 16:28 ` kbuild test robot
2015-11-01 18:37 ` Oleg Nesterov
2015-11-02 2:43 ` Fengguang Wu [this message]
2015-11-01 18:26 ` Oleg Nesterov
2015-11-01 21:48 ` 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=20151102024309.GA7966@wfg-t540p.sh.intel.com \
--to=lkp@intel$(echo .)com \
--cc=akpm@linux-foundation$(echo .)org \
--cc=axboe@fb$(echo .)com \
--cc=kbuild-all@01$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=mpa@pengutronix$(echo .)de \
--cc=oleg@redhat$(echo .)com \
--cc=sfr@canb$(echo .)auug.org.au \
/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