<html><body bgcolor="#FFFFFF"><div><br><br>On Sep 1, 2010, at 9:43, Grant Likely <<a href="mailto:grant.likely@secretlab.ca">grant.likely@secretlab.ca</a>> wrote:<br><font class="Apple-style-span" color="#0023A3"><font class="Apple-style-span" color="#000000"><br></font></font></div><blockquote type="cite"><div><span></span><br><span>In the interest of making driver code easier to write and review,</span><br><span>would you be opposed to a set of patches to remove the ERR_PTR()</span><br><span>pattern from phylib and its users?</span><br></div></blockquote><div><br></div><div><br></div><div>Not at all. I was trying to make sure all the information was available, and I'm not really a big fan of passing in a **ptr to get set. But I don't really have a strong opinion. This is just the design i settled on. Heck, 99.9% of the errors are unlikely to ever happen, a they're caused by hardware malfunction!</div><div><br></div><div>Andy</div><div><br></div><br><blockquote type="cite"><div><span></span><br><span>g.</span><br><span></span><br><span>-- </span><br><span>Grant Likely, B.Sc., P.Eng.</span><br><span>Secret Lab Technologies Ltd.</span><br><span></span><br></div></blockquote></body></html>