Re: [PATCH] Illustration of warning explosion silliness

[Jeff Garzik]

Andrew Morton wrote:
> > You're ignoring the API issue at hand.  Let me say it again for the 
> > cheap seats:  "search"  You search a list, and stick a pointer somewhere 
> > when found.  No hardware touched.  No allocations.  Real world.  There 
> > is an example of usage in the kernel today.
>
> If it's called in that fashion then the caller should still check the
> device_for_each_child() return value to find out if it actually got a
> match.


Or in the case of scsi_sysfs.c, it simply <does something>.

Oh well, whatever.  This thing introduces endless build noise we won't 
kill for years, making it much harder to spot much more serious stuff.

	Jeff


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