From: Giuseppe CAVALLARO <peppe.cavallaro@st.com>
To: Viresh Kumar <viresh.kumar@st.com>
Cc: netdev@vger.kernel.org, shiraz.hashim@st.com,
armando.visconti@st.com, deepak.sikri@st.com,
viresh.linux@gmail.com
Subject: Re: [PATCH] linux/stmmac.h: include <linux/platform_device.h> to remove compilation warning.
Date: Mon, 02 May 2011 14:46:09 +0200 [thread overview]
Message-ID: <4DBEA791.4010900@st.com> (raw)
In-Reply-To: <2239eca1d15014be7b6d94f883f9492dc1fbc60a.1304317552.git.viresh.kumar@st.com>
On 5/2/2011 8:30 AM, Viresh Kumar wrote:
> stmmac.h uses struct platform_device and doesn't include
> <linux/platform_device.h>. And so we get following compilation warning while
> using this file:
> warning: ‘struct platform_device’ declared inside parameter list
>
> This patch includes <linux/platform_device.h> in stmmac.h to remove this warning
Hi Viresh
thanks for the patch that looks good for me.
We could also remove this inclusion (see commit
1f0f63885658889b3bcb8a08fbcb9532f8e536c9) from
drivers/net/stmmac/stmmac.h and keep it in linux/stmmac.h as you suggested.
What do you think?
Regards
Peppe
> Signed-off-by: Viresh Kumar <viresh.kumar@st.com>
> ---
> include/linux/stmmac.h | 2 ++
> 1 files changed, 2 insertions(+), 0 deletions(-)
>
> diff --git a/include/linux/stmmac.h b/include/linux/stmmac.h
> index 73d9b4e..d7dfe7d 100644
> --- a/include/linux/stmmac.h
> +++ b/include/linux/stmmac.h
> @@ -26,6 +26,8 @@
> #ifndef __STMMAC_PLATFORM_DATA
> #define __STMMAC_PLATFORM_DATA
>
> +#include <linux/platform_device.h>
> +
> #define STMAC_TYPE_0 0
> #define STMAC_TYPE_1 1
> #define STMAC_TYPE_2 2
next prev parent reply other threads:[~2011-05-02 13:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-02 6:30 [PATCH] linux/stmmac.h: include <linux/platform_device.h> to remove compilation warning Viresh Kumar
2011-05-02 12:46 ` Giuseppe CAVALLARO [this message]
2011-05-03 3:45 ` viresh kumar
2011-05-02 22:01 ` David Miller
2011-05-03 3:44 ` viresh kumar
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=4DBEA791.4010900@st.com \
--to=peppe.cavallaro@st.com \
--cc=armando.visconti@st.com \
--cc=deepak.sikri@st.com \
--cc=netdev@vger.kernel.org \
--cc=shiraz.hashim@st.com \
--cc=viresh.kumar@st.com \
--cc=viresh.linux@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;
as well as URLs for NNTP newsgroup(s).