From: Lee Jones <lee.jones@linaro.org>
To: Jassi Brar <jaswinder.singh@linaro.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, lkml <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: build failure after merge of the mailbox tree
Date: Wed, 4 Nov 2015 08:16:10 +0000 [thread overview]
Message-ID: <20151104081610.GG3503@x1> (raw)
In-Reply-To: <CAJe_Zhe3iL=H9E1uVTLv959eVYDxzZMre8D6m8iOJbzDsFg0Nw@mail.gmail.com>
On Wed, 04 Nov 2015, Jassi Brar wrote:
> On 1 November 2015 at 17:42, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> > Hi Jassi,
> >
> > After merging the mailbox tree, today's linux-next build (x86_64
> > allmodconfig) failed like this:
> >
> > drivers/mailbox/mailbox-test.c: In function 'mbox_test_receive_message':
> > drivers/mailbox/mailbox-test.c:226:11: error: implicit declaration of function '__io_virt' [-Werror=implicit-function-declaration]
> > __io_virt(tdev->mmio), MBOX_MAX_MSG_LEN, true);
> > ^
> >
> > Caused by commit
> >
> > a133f8b65d59 ("mailbox: mailbox-test: Correctly repair Sparse warnings")
> >
> > I have used the mailbox tree from next-20151022 for today.
> >
> Lee, would you please send a fix for your last fix please?
I was about to take a look at this, but it looks like you fixed it already.
--
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
next prev parent reply other threads:[~2015-11-04 8:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-01 12:12 linux-next: build failure after merge of the mailbox tree Stephen Rothwell
2015-11-04 2:57 ` Jassi Brar
2015-11-04 8:16 ` Lee Jones [this message]
2017-03-29 5:17 Stephen Rothwell
2023-08-31 1:00 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=20151104081610.GG3503@x1 \
--to=lee.jones@linaro.org \
--cc=jaswinder.singh@linaro.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).