From: broonie@opensource.wolfsonmicro.com (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] regulator: anatop: fix 'anatop_regulator' name collision
Date: Mon, 2 Apr 2012 23:29:12 +0100 [thread overview]
Message-ID: <20120402222911.GO3160@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1333349821-5844-1-git-send-email-shawn.guo@linaro.org>
On Mon, Apr 02, 2012 at 02:57:01PM +0800, Shawn Guo wrote:
> There is a name collision between 'struct platform_driver
> anatop_regulator' and 'struct anatop_regulator', which causes some
> section mismatch warnings like below.
Applied, thanks.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20120402/e7ff68c7/attachment.sig>
prev parent reply other threads:[~2012-04-02 22:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-02 6:57 [PATCH] regulator: anatop: fix 'anatop_regulator' name collision Shawn Guo
2012-04-02 22:29 ` 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=20120402222911.GO3160@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).