From: Arnd Bergmann <arnd@arndb.de>
To: Linus Walleij <linus.walleij@stericsson.com>
Cc: linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Stephen Warren <swarren@nvidia.com>,
Anmar Oueja <anmar.oueja@linaro.org>,
Patrice Chotard <patrice.chotard@st.com>,
Linus Walleij <linus.walleij@linaro.org>
Subject: Re: [PATCH v2] pinctrl: move subsystem mutex to pinctrl_dev struct
Date: Fri, 26 Apr 2013 16:43:32 +0200 [thread overview]
Message-ID: <2852417.oyEN2DhaoE@wuerfel> (raw)
In-Reply-To: <1366794119-766-1-git-send-email-linus.walleij@stericsson.com>
On Wednesday 24 April 2013 11:01:59 Linus Walleij wrote:
> /**
> - * pinctrl_lookup_state() - retrieves a state handle from a pinctrl handle
> - * @p: the pinctrl handle to retrieve the state from
> - * @name: the state name to retrieve
> + * pinctrl_select_state() - select/activate/program a pinctrl state to HW
> + * @p: the pinctrl handle for the device that requests configuration
> + * @state: the state handle to select/activate/program
> */
> -struct pinctrl_state *pinctrl_lookup_state(struct pinctrl *p, const char *name)
> -{
> - struct pinctrl_state *s;
> -
> - mutex_lock(&pinctrl_mutex);
> - s = pinctrl_lookup_state_locked(p, name);
> - mutex_unlock(&pinctrl_mutex);
> -
> - return s;
> -}
> -EXPORT_SYMBOL_GPL(pinctrl_lookup_state);
> -
> -static int pinctrl_select_state_locked(struct pinctrl *p,
> - struct pinctrl_state *state)
> +int pinctrl_select_state(struct pinctrl *p, struct pinctrl_state *state)
> {
> struct p
This showed up in linux-next and broke a lot of driver modules, since you
remove the EXPORT_SYMBOL_GPL(pinctrl_lookup_state) line.
Arnd
next prev parent reply other threads:[~2013-04-26 14:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-24 9:01 [PATCH v2] pinctrl: move subsystem mutex to pinctrl_dev struct Linus Walleij
2013-04-26 14:43 ` Arnd Bergmann [this message]
2013-04-26 14:59 ` 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=2852417.oyEN2DhaoE@wuerfel \
--to=arnd@arndb.de \
--cc=anmar.oueja@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linus.walleij@stericsson.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patrice.chotard@st.com \
--cc=swarren@nvidia.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