From: Mohammed Shafi <mshajakhan@atheros.com>
To: "linville@tuxdriver.com" <linville@tuxdriver.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
Randy Dunlap <randy.dunlap@oracle.com>
Subject: Re: [PATCH] mac80211: Fix a compilation warning
Date: Mon, 18 Apr 2011 15:49:00 +0530 [thread overview]
Message-ID: <4DAC1014.7020303@atheros.com> (raw)
In-Reply-To: <1303104058-18958-1-git-send-email-mshajakhan@atheros.com>
On Monday 18 April 2011 10:50 AM, Mohammed Shajakhan wrote:
> From: Mohammed Shafi Shajakhan<mshajakhan@atheros.com>
>
> mac80211/debugfs_sta.c:113: warning:
> format ‘%d’ expects type ‘int’, but argument 4 has type ‘long int’
> introduced by the commit ebe27c91af8b7f4810ae906fbd3eeb2d87850026
>
> Signed-off-by: Mohammed Shafi Shajakhan<mshajakhan@atheros.com>
> ---
> net/mac80211/debugfs_sta.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/net/mac80211/debugfs_sta.c b/net/mac80211/debugfs_sta.c
> index c008232..a01d213 100644
> --- a/net/mac80211/debugfs_sta.c
> +++ b/net/mac80211/debugfs_sta.c
> @@ -108,7 +108,7 @@ static ssize_t sta_connected_time_read(struct file *file, char __user *userbuf,
> result.tm_year -= 70;
> result.tm_mday -= 1;
> res = scnprintf(buf, sizeof(buf),
> - "years - %d\nmonths - %d\ndays - %d\nclock - %d:%d:%d\n\n",
> + "years - %ld\nmonths - %d\ndays - %d\nclock - %d:%d:%d\n\n",
> result.tm_year, result.tm_mon, result.tm_mday,
> result.tm_hour, result.tm_min, result.tm_sec);
> return simple_read_from_buffer(userbuf, count, ppos, buf, res);
>
John, this seems to be already fixed by this patch
[PATCH -next] mac80211: fix debugfs printk format warning
http://www.spinics.net/lists/linux-wireless/msg67977.html
prev parent reply other threads:[~2011-04-18 10:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-18 5:20 [PATCH] mac80211: Fix a compilation warning Mohammed Shafi Shajakhan
2011-04-18 10:19 ` Mohammed Shafi [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=4DAC1014.7020303@atheros.com \
--to=mshajakhan@atheros.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=randy.dunlap@oracle.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).