From: Harvey Harrison <harvey.harrison@gmail.com>
To: Andy Walls <awalls@radix.net>
Cc: LKML <linux-kernel@vger.kernel.org>,
v4l-maintainer <v4l-dvb-maintainer@linuxtv.org>,
Andrew Morton <akpm@linux-foundation.org>,
Mauro Carvalho Chehab <mchehab@infradead.org>
Subject: Re: [v4l-dvb-maintainer] [PATCH] dvb: usb vendor_ids/product_ids are __le16
Date: Fri, 14 Nov 2008 13:08:45 -0800 [thread overview]
Message-ID: <1226696926.5483.48.camel@brick> (raw)
In-Reply-To: <1226696157.3312.92.camel@palomino.walls.org>
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
next prev parent reply other threads:[~2008-11-14 21:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-14 18:19 [PATCH] dvb: usb vendor_ids/product_ids are __le16 Harvey Harrison
2008-11-14 19:05 ` [v4l-dvb-maintainer] " Michael Krufky
2008-11-14 19:07 ` Harvey Harrison
2008-11-14 19:15 ` Michael Krufky
2008-11-14 19:20 ` Harvey Harrison
2008-11-14 19:25 ` Devin Heitmueller
2008-11-14 19:44 ` Harvey Harrison
2008-11-14 20:55 ` Andy Walls
2008-11-14 21:08 ` Harvey Harrison [this message]
2008-11-15 10:42 ` Hans Verkuil
2008-11-15 7:21 ` Jean-Francois Moine
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=1226696926.5483.48.camel@brick \
--to=harvey.harrison@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=awalls@radix.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@infradead.org \
--cc=v4l-dvb-maintainer@linuxtv.org \
/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