linux-kernel - Re: [v4l-dvb-maintainer] [PATCH] dvb: usb vendor_ids/product_ids are _

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: <1226696926.5483.48.camel@brick>
Date:	Fri, 14 Nov 2008 13:08:45 -0800
From:	Harvey Harrison <harvey.harrison@...il.com>
To:	Andy Walls <awalls@...ix.net>
Cc:	LKML <linux-kernel@...r.kernel.org>,
	v4l-maintainer <v4l-dvb-maintainer@...uxtv.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Mauro Carvalho Chehab <mchehab@...radead.org>
Subject: Re: [v4l-dvb-maintainer] [PATCH] dvb: usb vendor_ids/product_ids
 are __le16

On Fri, 2008-11-14 at 15:55 -0500, Andy Walls wrote:
> On Fri, 2008-11-14 at 11:44 -0800, Harvey Harrison wrote:
> 
> > But I'd suggest
> > that if you want to improve the maintainability of this code that someone
> > in v4l-land start running sparse regularly 
> 
> For those who don't get the daily 'bot mail on the v4l-dvb-maintainer
> list, Hans Verkuil's v4l-dvb build 'bot runs sparse builds daily for all
> of v4l-dvb land:
> 
> http://linuxtv.org/pipermail/v4l-dvb-maintainer/2008-November/008595.html
> 
> Although developers won't see waring/error outputs from those runs until
> after their changes are merged in the main v4l-dvb repo.
> 
> The latest kernel this automatic sparse build compiles is currently
> 2.26.28-rc4.  I've used it to monitor the cx18 driver for sparse build
> errors so I could address them - it's quite convenient.
> 

Does Hans' build turn on __CHECK_ENDIAN__? That would help as well.

Harvey

--
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/