From: Mark Brown <broonie@kernel.org>
To: Thiago Farina <tfransosi@gmail.com>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
linux list <linux-kernel@vger.kernel.org>,
linaro-kernel@lists.linaro.org
Subject: Re: [PATCH] regulator: core: Split devres code out into a separate file
Date: Thu, 12 Sep 2013 10:43:31 +0100 [thread overview]
Message-ID: <20130912094331.GB29403@sirena.org.uk> (raw)
In-Reply-To: <CACnwZYeNe4T27eqiQ+LW-ot9Hk8Qk0Uzg7b3jH7xF_euHOWYhQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 252 bytes --]
On Wed, Sep 11, 2013 at 02:15:51PM -0300, Thiago Farina wrote:
> don't you need any forward declaration here nor any include (like for
> list_head and device_attribute)?
Probably, though all the users should have pulled in the regulator API
headers.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2013-09-12 9:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-11 12:19 Mark Brown
2013-09-11 17:15 ` Thiago Farina
2013-09-12 9:43 ` Mark Brown [this message]
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=20130912094331.GB29403@sirena.org.uk \
--to=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tfransosi@gmail.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
all inboxes | Powered by JetHome®