From: r.schwebel@pengutronix.de (Robert Schwebel)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: mxc: add missing include
Date: Thu, 26 Jan 2012 11:59:42 +0100 [thread overview]
Message-ID: <20120126105942.GF20173@pengutronix.de> (raw)
In-Reply-To: <20120126111011.GA3523@S2101-09.ap.freescale.net>
On Thu, Jan 26, 2012 at 07:10:14PM +0800, Shawn Guo wrote:
> Fabio had posted a patch below to fix the same issue, which is still
> pending on Sascha to apply.
>
> http://www.spinics.net/lists/arm-kernel/msg154514.html
>
> IMO, Fabio's the fixing is better than this patch, since we do not
> necessarily need '__init' annotation for function prototype declaration.
Ok, sounds good.
rsc
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
prev parent reply other threads:[~2012-01-26 10:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-26 10:43 [PATCH] ARM: mxc: add missing include Robert Schwebel
2012-01-26 11:10 ` Shawn Guo
2012-01-26 10:59 ` Robert Schwebel [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=20120126105942.GF20173@pengutronix.de \
--to=r.schwebel@pengutronix.de \
--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).