linux-kernel - Re: linux-next: build warning after merge of the driver-core tree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Thu, 2 Sep 2010 12:59:53 -0700
From:	Greg KH <greg@...ah.com>
To:	Thomas Renninger <trenn@...e.de>
Cc:	Stephen Rothwell <sfr@...b.auug.org.au>,
	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
	Jason Baron <jbaron@...hat.com>
Subject: Re: linux-next: build warning after merge of the driver-core tree

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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/