linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	Mark Allyn <mark.a.allyn@intel.com>,
	Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
	Alan Cox <alan@linux.intel.com>
Subject: Re: linux-next: build warnings after merge of the staging tree
Date: Mon, 30 Jan 2012 21:14:42 -0800	[thread overview]
Message-ID: <20120131051442.GA25054@kroah.com> (raw)
In-Reply-To: <20120131142521.852ecb04b07f7174c179b3c8@canb.auug.org.au>

On Tue, Jan 31, 2012 at 02:25:21PM +1100, Stephen Rothwell wrote:
> Hi Greg,
> 
> After merging the staging tree, today's linux-next build (x86_64
> allmodconfig) produced these warnings:
> 
> drivers/staging/sep/sep_main.c: In function 'sep_allocate_dmatables_region':
> drivers/staging/sep/sep_main.c:217:2: warning: format '%X' expects argument of type 'unsigned int', but argument 5 has type 'size_t' [-Wformat]
> drivers/staging/sep/sep_main.c: In function 'sep_activate_msgarea_context':
> drivers/staging/sep/sep_main.c:3348:5: warning: format '%X' expects argument of type 'unsigned int', but argument 4 has type 'size_t' [-Wformat]
> drivers/staging/sep/sep_main.c: In function 'sep_create_msgarea_context':
> drivers/staging/sep/sep_main.c:3380:5: warning: format '%X' expects argument of type 'unsigned int', but argument 4 has type 'size_t' [-Wformat]
> drivers/staging/sep/sep_main.c: In function 'sep_read':
> drivers/staging/sep/sep_main.c:3466:2: warning: format '%X' expects argument of type 'unsigned int', but argument 5 has type 'size_t' [-Wformat]
> drivers/staging/sep/sep_main.c: In function 'sep_fastcall_args_get':
> drivers/staging/sep/sep_main.c:3526:5: warning: format '%X' expects argument of type 'unsigned int', but argument 4 has type 'size_t' [-Wformat]
> drivers/staging/sep/sep_main.c:3567:5: warning: format '%X' expects argument of type 'unsigned int', but argument 4 has type 'size_t' [-Wformat]
> drivers/staging/sep/sep_main.c:3567:5: warning: format '%X' expects argument of type 'unsigned int', but argument 5 has type 'size_t' [-Wformat]
> 
> Introduced by commit ff3d9c3c90c6 ("staging: sep: SEP update").

Thanks, I've already told Alan about them, he said he would resolve them
soon.

greg k-h

  reply	other threads:[~2012-01-31  5:15 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-31  3:25 linux-next: build warnings after merge of the staging tree Stephen Rothwell
2012-01-31  5:14 ` Greg KH [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-05-06  4:10 Stephen Rothwell
2015-05-06  6:56 ` Julia Lawall
2015-05-29 10:40 Stephen Rothwell
2015-06-01  8:50 ` Stephen Rothwell
2015-06-20 10:48   ` Stephen Rothwell
2015-06-20 14:50     ` Greg KH
2017-07-31  5:02 Stephen Rothwell
2017-08-09  1:25 ` Stephen Rothwell
2017-08-22  1:49   ` Stephen Rothwell
2017-08-17 17:57 ` Greg KH
2017-08-18 12:02   ` JB Van Puyvelde
2017-11-02  4:38 Stephen Rothwell
2018-05-14  4:34 Stephen Rothwell
2018-05-14  9:26 ` Greg KH
2019-02-05  3:22 Stephen Rothwell
2019-02-05 10:24 ` Jonathan Cameron

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=20120131051442.GA25054@kroah.com \
    --to=greg@kroah.com \
    --cc=alan@linux.intel.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mark.a.allyn@intel.com \
    --cc=sfr@canb.auug.org.au \
    /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).