> On Mon, Dec 09, 2013 at 01:55:53PM +1000, David Gwynne wrote:
> > this is a demonstration of using TIMEOUT_INITIALIZED().
> >
> > because we know the timeout is always set up correctly, we dont
> > have to test for it all over the place.
> >
>
> [a bit of snipping...]
>
> > - if (timeout_in
On Mon, Dec 09, 2013 at 10:18:06PM +1000, David Gwynne wrote:
>
> On 9 Dec 2013, at 10:01 pm, David Gwynne wrote:
>
> >
> > On 9 Dec 2013, at 6:59 pm, Bret Lambert wrote:
> >
> >> On Mon, Dec 09, 2013 at 01:55:53PM +1000, David Gwynne wrote:
> >>> this is a demonstration of using TIMEOUT_INIT
On 9 Dec 2013, at 10:01 pm, David Gwynne wrote:
>
> On 9 Dec 2013, at 6:59 pm, Bret Lambert wrote:
>
>> On Mon, Dec 09, 2013 at 01:55:53PM +1000, David Gwynne wrote:
>>> this is a demonstration of using TIMEOUT_INITIALIZED().
>>>
>>> because we know the timeout is always set up correctly, we
On 9 Dec 2013, at 6:59 pm, Bret Lambert wrote:
> On Mon, Dec 09, 2013 at 01:55:53PM +1000, David Gwynne wrote:
>> this is a demonstration of using TIMEOUT_INITIALIZED().
>>
>> because we know the timeout is always set up correctly, we dont
>> have to test for it all over the place.
>>
>
> [a
On Mon, Dec 09, 2013 at 01:55:53PM +1000, David Gwynne wrote:
> this is a demonstration of using TIMEOUT_INITIALIZED().
>
> because we know the timeout is always set up correctly, we dont
> have to test for it all over the place.
>
[a bit of snipping...]
> - if (timeout_initialized(&rnd_tim
this is a demonstration of using TIMEOUT_INITIALIZED().
because we know the timeout is always set up correctly, we dont
have to test for it all over the place.
Index: rnd.c
===
RCS file: /cvs/src/sys/dev/rnd.c,v
retrieving revision 1