From: Artem Bityutskiy <dedekind1@gmail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: build failure after merge of the l2-mtd tree
Date: Tue, 07 Feb 2012 10:02:06 +0200 [thread overview]
Message-ID: <1328601726.22240.45.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <20120207135815.b551929e844a3824d7943e76@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 935 bytes --]
On Tue, 2012-02-07 at 13:58 +1100, Stephen Rothwell wrote:
> Hi Artem,
>
> After merging the l2-mtd tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> drivers/mtd/devices/pmc551.c: In function 'pmc551_erase':
> drivers/mtd/devices/pmc551.c:157:2: error: implicit declaration of function 'pmc551_point' [-Werror=implicit-function-declaration]
> drivers/mtd/devices/pmc551.c: At top level:
> drivers/mtd/devices/pmc551.c:194:12: error: static declaration of 'pmc551_point' follows non-static declaration
> drivers/mtd/devices/pmc551.c:157:2: note: previous implicit declaration of 'pmc551_point' was here
> drivers/mtd/devices/pmc551.c: In function 'pmc551_unpoint':
> drivers/mtd/devices/pmc551.c:229:1: warning: no return statement in function returning non-void [-Wreturn-type]
Hi, thanks a lot, I missed this. Fixed and build-tested with ARCH=i386.
--
Best Regards,
Artem Bityutskiy
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-02-07 8:00 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-07 2:58 linux-next: build failure after merge of the l2-mtd tree Stephen Rothwell
2012-02-07 8:02 ` Artem Bityutskiy [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-08-28 2:19 Stephen Rothwell
2017-08-28 22:06 ` Brian Norris
2017-02-09 1:08 Stephen Rothwell
2017-02-09 1:59 ` Brian Norris
2017-02-09 1:59 ` Brian Norris
2016-07-19 0:59 Stephen Rothwell
2016-07-19 1:20 ` Brian Norris
2016-07-19 1:46 ` Stephen Rothwell
2015-12-21 5:47 Stephen Rothwell
2015-09-30 5:16 Stephen Rothwell
2014-05-22 5:30 Stephen Rothwell
2014-05-26 17:42 ` Brian Norris
2014-05-26 23:59 ` Stephen Rothwell
2014-05-27 10:40 ` Artem Bityutskiy
2014-05-27 22:49 ` Stephen Rothwell
2012-10-12 0:14 Stephen Rothwell
2012-10-12 4:51 ` Dinh Nguyen
2012-10-12 4:51 ` Dinh Nguyen
2012-10-18 0:28 ` Stephen Rothwell
2012-10-18 9:26 ` Artem Bityutskiy
2012-02-06 1:07 Stephen Rothwell
2012-02-06 1:07 ` Stephen Rothwell
2012-02-06 9:14 ` Artem Bityutskiy
2012-02-06 9:14 ` Artem Bityutskiy
2012-02-06 21:10 ` Stephen Rothwell
2012-02-06 21:10 ` 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=1328601726.22240.45.camel@sauron.fi.intel.com \
--to=dedekind1@gmail.com \
--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 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.