From: Wolfram Sang <wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.org>
To: Pascal Huerst <pascal.huerst-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: tony-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org,
linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] omap: i2c: Add calls for pinctrl state select
Date: Thu, 23 Apr 2015 13:31:13 +0200 [thread overview]
Message-ID: <20150423113113.GA19918@katana> (raw)
In-Reply-To: <55377C9E.5090904-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 642 bytes --]
On Wed, Apr 22, 2015 at 12:49:02PM +0200, Pascal Huerst wrote:
>
>
> On 22.04.2015 12:28, Wolfram Sang wrote:
> > I assume you have a different kernel config where something is enabled
> > which includes the pinctrl-stuff in another include which is included
> > by these drivers. Although, my .config was arm-allyesconfig. Can you
> > send yours?
>
> Sure. See below.
Thanks. device.h includes pinctrl/devinfo.h which includes
pinctrl/consumer.h iff CONFIG_PINCTRL is enabled. So, seems my
build-system didn't pick allyesconfig but another config with PINCTRL
disabled. Will fix the st driver now, thanks for reporting!
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-04-23 11:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-17 15:07 [PATCH] omap: i2c: Add calls for pinctrl state select pascal.huerst-Re5JQEeQqe8AvxtiuMwx3w
2015-04-22 8:12 ` Wolfram Sang
2015-04-22 8:50 ` Pascal Huerst
2015-04-22 10:28 ` Wolfram Sang
2015-04-22 10:49 ` Pascal Huerst
[not found] ` <55377C9E.5090904-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-04-23 11:31 ` Wolfram Sang [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-04-16 17:04 pascal.huerst-Re5JQEeQqe8AvxtiuMwx3w
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=20150423113113.GA19918@katana \
--to=wsa-z923lk4zbo2bacvfa/9k2g@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=pascal.huerst-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=tony-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.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).