From: Paul Gortmaker <paul.gortmaker@windriver.com>
To: Steven Miao <realmz6@gmail.com>
Cc: "linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: [blackfin] gpio_request build fail on linux-next bisected
Date: Tue, 22 Apr 2014 12:21:06 -0400 [thread overview]
Message-ID: <535696F2.6010009@windriver.com> (raw)
Hi Steven,
This linux-next build fail:
http://kisskb.ellerman.id.au/kisskb/buildresult/10940572/
which fails like this:
CC arch/blackfin/mach-bf533/boards/stamp.o
arch/blackfin/mach-bf533/boards/stamp.c: In function 'stamp_init':
arch/blackfin/mach-bf533/boards/stamp.c:874:2: error: implicit declaration of function 'gpio_request'
arch/blackfin/mach-bf533/boards/stamp.c:876:3: error: implicit declaration of function 'gpio_direction_output'
arch/blackfin/mach-bf533/boards/stamp.c:877:3: error: implicit declaration of function 'gpio_free'
make[1]: *** [arch/blackfin/mach-bf533/boards/stamp.o] Error 1
...bisects as follows:
a0c1fb2ea74dedecd303fb0388e21ca869239db2 is the first bad commit
commit a0c1fb2ea74dedecd303fb0388e21ca869239db2
Author: Steven Miao <realmz6@gmail.com>
Date: Mon Mar 17 13:36:51 2014 +0800
blackfin: portmux: cleanup head file
drop unused head file
change pinmux request/free macro for backward compatiblity
add function declaration
Signed-off-by: Steven Miao <realmz6@gmail.com>
:040000 040000 6bf439b9ec79ab17c87afe720ef23e2a01ee1c1f 6a67fdde171be53f3bfd0fd290f270fbca104542 M arch
bisect run success
Since the failure is now in mainline/master, the fix should
be aimed at rc3 and not be specific to linux-next.
Thanks,
Paul.
reply other threads:[~2014-04-22 16:20 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=535696F2.6010009@windriver.com \
--to=paul.gortmaker@windriver.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=realmz6@gmail.com \
/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