From: Randy Dunlap <rdunlap@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>, linux-next@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, linux-gpio@vger.kernel.org,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Arnd Bergmann <arnd@arndb.de>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: linux-next: Tree for Jun 27 (pinctrl && !CONFIG_OF)
Date: Mon, 27 Jun 2016 11:15:25 -0700 [thread overview]
Message-ID: <57716D3D.4070302@infradead.org> (raw)
In-Reply-To: <20160627163939.20e454d5@canb.auug.org.au>
On 06/26/16 23:39, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20160624:
>
on i386, when CONFIG_OF is not enabled ...
but OF_GPIO is enabled due to this in drivers/gpio/Kconfig:
config OF_GPIO
def_bool y
depends on OF || COMPILE_TEST
(above from commit 1e4a80640338924b9f9fd7a121ac31d08134410a
from Alexander Stein <alexanders83@web.de>)
../drivers/pinctrl/bcm/pinctrl-iproc-gpio.c:381:20: error: 'pinconf_generic_dt_node_to_map_pin' undeclared here (not in a function)
../drivers/pinctrl/bcm/pinctrl-cygnus-mux.c:739:20: error: 'pinconf_generic_dt_node_to_map_group' undeclared here (not in a function)
../drivers/pinctrl/bcm/pinctrl-nsp-gpio.c:365:20: error: 'pinconf_generic_dt_node_to_map_pin' undeclared here (not in a function)
because that function is only present when CONFIG_OF is enabled.
Also, why does that commit (1e4a80640338924b9f9fd7a121ac31d08134410a)
not have any other S-O-B lines in it? like whoever merged it?
--
~Randy
next parent reply other threads:[~2016-06-27 18:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20160627163939.20e454d5@canb.auug.org.au>
2016-06-27 18:15 ` Randy Dunlap [this message]
2016-06-27 21:36 ` linux-next: Tree for Jun 27 (pinctrl && !CONFIG_OF) Arnd Bergmann
2016-06-28 7:00 ` Alexander Stein
2016-06-28 8:25 ` Randy Dunlap
2016-06-28 8:37 ` Arnd Bergmann
2016-06-29 5:54 ` Alexander Stein
2016-07-04 9:46 ` Linus Walleij
2016-07-04 16:12 ` Randy Dunlap
2016-07-05 6:48 ` Linus Walleij
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=57716D3D.4070302@infradead.org \
--to=rdunlap@infradead.org \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=torvalds@linux-foundation.org \
/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).