From: Greg KH <greg@kroah.com>
To: Thomas Renninger <trenn@suse.de>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Jason Baron <jbaron@redhat.com>
Subject: Re: linux-next: build warning after merge of the driver-core tree
Date: Thu, 2 Sep 2010 12:59:53 -0700 [thread overview]
Message-ID: <20100902195953.GA16897@kroah.com> (raw)
In-Reply-To: <201009021214.27970.trenn@suse.de>
On Thu, Sep 02, 2010 at 12:14:27PM +0200, Thomas Renninger wrote:
> On Thursday 02 September 2010 05:29:11 Greg KH wrote:
> > On Thu, Sep 02, 2010 at 01:18:35PM +1000, Stephen Rothwell wrote:
> > > Hi Greg,
> ...
> > > kernel/params.c: In function 'parse_args':
> > > kernel/params.c:200: warning: passing argument 2 of 'snprintf' makes integer from pointer without a cast
> > > include/linux/kernel.h:203: note: expected 'size_t' but argument is of type 'char *'
> > >
> > > Caused by commit d1aa8e2ab38942b21d543611d4f829597d8791d4 ("Dynamic
> > > Debug: Introduce global fake module param module.ddebug").
> > >
> > > Some warnings should not be ignored ... and it does make me wonder how
> > > much testing this has had ...
> Strange, I tried this out and it worked, I doubt that this version could.
> Possibly it slipped in when getting dddebug patches together for resending
> to Greg, no idea.
Ok, I've replaced it with this version, looks better.
thanks,
greg k-h
next prev parent reply other threads:[~2010-09-02 20:11 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-02 3:18 linux-next: build warning after merge of the driver-core tree Stephen Rothwell
2010-09-02 3:29 ` Greg KH
2010-09-02 10:14 ` Thomas Renninger
2010-09-02 19:59 ` Greg KH [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-02-21 5:37 Stephen Rothwell
2011-02-21 5:50 ` Stephen Rothwell
2011-02-21 6:31 ` Greg KH
2011-03-17 23:10 ` Stephen Rothwell
2011-03-17 23:10 ` Stephen Rothwell
2011-02-21 6:02 Stephen Rothwell
2011-02-21 6:02 ` Stephen Rothwell
2011-02-21 6:32 ` Greg KH
2011-02-21 20:18 ` Ilya Yanok
2013-06-25 8:33 Stephen Rothwell
2013-06-25 12:00 ` Ming Lei
2015-10-07 4:51 Stephen Rothwell
2015-10-07 6:40 ` Viresh Kumar
2015-10-07 21:48 ` Rafael J. Wysocki
2015-10-07 22:04 ` Stephen Rothwell
2015-10-07 22:47 ` Rafael J. Wysocki
2015-10-08 7:09 ` Viresh Kumar
2015-10-08 20:30 ` Rafael J. Wysocki
2015-10-09 5:36 ` Stephen Rothwell
2015-10-09 6:31 ` Viresh Kumar
2015-10-09 20:49 ` Rafael J. Wysocki
2015-10-09 6:37 ` Viresh Kumar
2019-07-04 6:17 Stephen Rothwell
2019-07-04 6:30 ` Greg KH
2019-07-04 6:24 Stephen Rothwell
2019-07-04 8:21 ` Greg KH
2019-08-01 5:05 Stephen Rothwell
2019-08-01 6:10 ` Greg KH
2019-08-05 3:04 Stephen Rothwell
2019-08-05 4:56 ` Stephen Rothwell
2019-08-06 0:03 ` Saravana Kannan
2020-09-09 7:23 Stephen Rothwell
2020-09-09 7:40 ` Greg KH
2021-12-06 8:30 Stephen Rothwell
2021-12-06 12:53 ` Heiko Carstens
2021-12-07 10:23 ` Greg KH
2022-05-01 22:36 Stephen Rothwell
2023-02-20 5:31 Stephen Rothwell
2023-02-20 7:26 ` Qi Zheng
2023-02-20 7:31 ` Greg KH
2023-02-20 9:49 ` Bagas Sanjaya
2023-02-20 10:15 ` Qi Zheng
2023-02-20 10:50 ` Greg KH
2023-02-20 11:01 ` Qi Zheng
2023-03-27 1:03 Stephen Rothwell
2023-03-27 7:31 ` Greg KH
2024-11-07 11:35 Stephen Rothwell
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=20100902195953.GA16897@kroah.com \
--to=greg@kroah.com \
--cc=jbaron@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=trenn@suse.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.