linux-kernel - Re: [PATCH] drivers:staging: fix compilation warning

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <20121203110428.GA22681@gmail.com>
Date:	Mon, 3 Dec 2012 11:04:29 +0000
From:	Cong Ding <dinggnu@...il.com>
To:	Dan Carpenter <dan.carpenter@...cle.com>
Cc:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Adam Buchbinder <adam.buchbinder@...il.com>,
	Jesper Juhl <jj@...osbits.net>,
	Uwe Kleine-König <uwe@...ine-koenig.org>,
	devel@...verdev.osuosl.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] drivers:staging: fix compilation warning

On Mon, Dec 03, 2012 at 01:56:09PM +0300, Dan Carpenter wrote:
> On Mon, Dec 03, 2012 at 10:34:08AM +0000, Cong Ding wrote:
> > We do not allow old-style function definition.  Always spell foo(void) if
> > a function does not take any parameters.
> > 
> 
> You should be working against linux-next.  This driver has been
> deleted in linux-next.
> 
> The subject should have been:
> [PATCH] Staging: telephony/ixj: fix sparse warning
> or something like that.  "drivers" is not useful.  And Staging by
> itself is too broad.
> 
> I think it's a Sparse warning, not a compile warning?  Copy and
> paste the warning into the commit message.
sure, thanks for the suggestions. 

- cong

> 
> Anyway, since this was deleted it doesn't matter.
> 
> regards,
> dan carpenter
> 
--
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/