From: Mark Brown <broonie@kernel.org>
To: Raag Jadav <raagjadav@gmail.com>
Cc: linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Liam Girdwood <lgirdwood@gmail.com>
Subject: Re: [PATCH v2 1/2] regulator: act8865: operating mode and suspend state support
Date: Thu, 15 Aug 2019 17:52:44 +0100 [thread overview]
Message-ID: <20190815165244.GA54921@sirena.co.uk> (raw)
In-Reply-To: <1565721176-8955-2-git-send-email-raagjadav@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 515 bytes --]
On Wed, Aug 14, 2019 at 12:02:55AM +0530, Raag Jadav wrote:
> Implement ->set_mode(), ->get_mode() and ->set_suspend_xx() hooks
> for act8865 with unlocked expert registers.
This breaks the build because it depends on patch 2:
drivers/regulator/act8865-regulator.c:22:10: fatal error: dt-bindings/regulator/active-semi,8865-regulator.h: No such file or directory
#include <dt-bindings/regulator/active-semi,8865-regulator.h>
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
compilation terminated.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-08-15 16:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-13 18:32 [PATCH v2 0/2] act8865 regulator modes and suspend states Raag Jadav
2019-08-13 18:32 ` [PATCH v2 1/2] regulator: act8865: operating mode and suspend state support Raag Jadav
2019-08-15 16:52 ` Mark Brown [this message]
2019-08-15 17:14 ` Applied "regulator: act8865: operating mode and suspend state support" to the regulator tree Mark Brown
2019-08-13 18:32 ` [PATCH v2 2/2] dt-bindings: regulator: act8865 regulator modes and suspend states Raag Jadav
2019-08-15 17:14 ` Applied "regulator: act8865 regulator modes and suspend states" to the regulator tree Mark Brown
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=20190815165244.GA54921@sirena.co.uk \
--to=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=raagjadav@gmail.com \
--cc=robh+dt@kernel.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
all inboxes | Powered by JetHome®