From: Alexander Stein <alexander.stein@systec-electronic.com>
To: Mark Brown <broonie@kernel.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] regmap: Fix implicit inclusion of device.h
Date: Wed, 30 Mar 2016 12:35:10 +0200 [thread overview]
Message-ID: <1706748.7VJNZvYO89@ws-stein> (raw)
In-Reply-To: <1459280515-1006-1-git-send-email-broonie@kernel.org>
On Tuesday 29 March 2016 12:41:54, Mark Brown wrote:
> internal.h is using dev_name() but doesn't include device.h which
> defines it. Add an explicit include to avoid build problems due to
> this.
>
> Signed-off-by: Mark Brown <broonie@kernel.org>
> ---
> drivers/base/regmap/internal.h | 1 +
> 1 file changed, 1 insertion(+)
Tested-by: Alexander Stein <alexander.stein@systec-electronic.com>
Best regards,
Alexander
prev parent reply other threads:[~2016-03-30 10:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-29 19:41 [PATCH 1/2] regmap: Fix implicit inclusion of device.h Mark Brown
2016-03-29 19:41 ` [PATCH 2/2] regmap: mmio: Parse endianness definitions from DT Mark Brown
2016-03-30 10:36 ` Alexander Stein
2016-03-31 6:09 ` Krzysztof Kozlowski
2016-03-31 6:23 ` Krzysztof Kozlowski
2016-03-31 17:19 ` Mark Brown
2016-03-30 10:35 ` Alexander Stein [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=1706748.7VJNZvYO89@ws-stein \
--to=alexander.stein@systec-electronic.com \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.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