Hi
2013/2/14 Daniel Vetter :
> On Thu, Feb 14, 2013 at 06:53:42PM -0200, Paulo Zanoni wrote:
>> Hi
>>
>> 2013/2/9 Daniel Vetter :
>> > On Fri, Feb 08, 2013 at 05:35:19PM -0200, Paulo Zanoni wrote:
>> >> From: Paulo Zanoni
>> >>
>> >> Also add an "ignore" bit that avoids printing the message in tw
On Thu, Feb 14, 2013 at 06:53:42PM -0200, Paulo Zanoni wrote:
> Hi
>
> 2013/2/9 Daniel Vetter :
> > On Fri, Feb 08, 2013 at 05:35:19PM -0200, Paulo Zanoni wrote:
> >> From: Paulo Zanoni
> >>
> >> Also add an "ignore" bit that avoids printing the message in two
> >> cases:
> >> - When the messag
Hi
2013/2/9 Daniel Vetter :
> On Fri, Feb 08, 2013 at 05:35:19PM -0200, Paulo Zanoni wrote:
>> From: Paulo Zanoni
>>
>> Also add an "ignore" bit that avoids printing the message in two
>> cases:
>> - When the message is in fact expected.
>> - After we get the first message. In tihs case, we e
On Fri, Feb 08, 2013 at 05:35:19PM -0200, Paulo Zanoni wrote:
> From: Paulo Zanoni
>
> Also add an "ignore" bit that avoids printing the message in two
> cases:
> - When the message is in fact expected.
> - After we get the first message. In tihs case, we expect to get
> hundreds of conse
From: Paulo Zanoni
Also add an "ignore" bit that avoids printing the message in two
cases:
- When the message is in fact expected.
- After we get the first message. In tihs case, we expect to get
hundreds of consecutive messages, so we just ignore all the
subsequent messages until the