From: Mark Brown <broonie@kernel.org>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
linux-kernel@vger.kernel.org,
Charles Keepax <ckeepax@opensource.cirrus.com>,
Bartosz Golaszewski <bgolaszewski@baylibre.com>,
Marek Szyprowski <m.szyprowski@samsung.com>,
Philipp Zabel <p.zabel@pengutronix.de>,
Petr Cvek <petr.cvek@tul.cz>,
Robert Jarzmik <robert.jarzmik@free.fr>,
Paul Parsons <lost.distance@yahoo.com>,
Kevin Hilman <khilman@baylibre.com>,
Neil Armstrong <narmstrong@baylibre.com>
Subject: Re: [PATCH 1/5 v9] regulator: gpio: Convert to use descriptors
Date: Thu, 24 Jan 2019 17:50:36 +0000 [thread overview]
Message-ID: <20190124175036.GF5641@sirena.org.uk> (raw)
In-Reply-To: <20190121091206.18239-1-linus.walleij@linaro.org>
[-- Attachment #1: Type: text/plain, Size: 443 bytes --]
On Mon, Jan 21, 2019 at 10:12:02AM +0100, Linus Walleij wrote:
> This converts the GPIO regulator driver to use decriptors only.
This patch breaks the build for me:
drivers/regulator/gpio-regulator.c: In function ‘gpio_regulator_probe’:
drivers/regulator/gpio-regulator.c:256:33: error: ‘dev’ undeclared (first use in this function); did you mean ‘pdev’?
drvdata->gpiods = devm_kzalloc(dev, sizeof(struct gpio_desc *),
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-01-24 17:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-21 9:12 Linus Walleij
2019-01-21 9:12 ` [PATCH 2/5 v9] regulator: fixed/gpio: Pull inversion/OD into gpiolib Linus Walleij
2019-01-21 9:12 ` [PATCH 3/5 v9] regulator: fixed/gpio: Update device tree bindings Linus Walleij
2019-01-21 9:12 ` [PATCH 4/5 v9] regulator: gpio: Simplify probe path Linus Walleij
2019-01-21 9:12 ` [PATCH 5/5 v9] regulator: core: Only support passing enable GPIO descriptors Linus Walleij
2019-01-24 17:50 ` Mark Brown [this message]
2019-01-26 12:22 ` [PATCH 1/5 v9] regulator: gpio: Convert to use descriptors 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=20190124175036.GF5641@sirena.org.uk \
--to=broonie@kernel.org \
--cc=bgolaszewski@baylibre.com \
--cc=ckeepax@opensource.cirrus.com \
--cc=khilman@baylibre.com \
--cc=lgirdwood@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lost.distance@yahoo.com \
--cc=m.szyprowski@samsung.com \
--cc=narmstrong@baylibre.com \
--cc=p.zabel@pengutronix.de \
--cc=petr.cvek@tul.cz \
--cc=robert.jarzmik@free.fr \
/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
all inboxes | Powered by JetHome®