All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Peres <martin.peres-Iz16wY1oaNPLSKGbIzaifA@public.gmane.org>
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: Re: Re-enable dithering after commit	a7b9f9e5adef276c25584e28ce9e520045ff048b
Date: Wed, 16 Jun 2010 19:24:03 +0200	[thread overview]
Message-ID: <4C1908B3.2060201@ensi-bourges.fr> (raw)
In-Reply-To: <4C187F74.4040402-Iz16wY1oaNPLSKGbIzaifA@public.gmane.org>

Le 16/06/2010 09:38, Martin Peres a écrit :
> Hi everyone,
>
> After commit a7b9f9e5adef276c25584e28ce9e520045ff048b, dithering has 
> disappeared on LVDS (for those who needed it).
>
> ThibG on IRC has bisected this behaviour to 
> a7b9f9e5adef276c25584e28ce9e520045ff048b. Here is a patch that 
> re-enables it.
>
> Please comment on it.
>
> Martin
Well, too late, Jerez already pushed a patch to do that :)

Do you have any idea of why it took almost 10 hours between the moment I 
sent this mail and the moment I actually received it from the list ? Is 
there a manual approbation somewhere to get rid of the spam ?

Thanks to Jerez for the patch anyway :) It works just as great and is 
better designed.

  parent reply	other threads:[~2010-06-16 17:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-16  7:38 Re-enable dithering after commit a7b9f9e5adef276c25584e28ce9e520045ff048b Martin Peres
     [not found] ` <4C187F74.4040402-Iz16wY1oaNPLSKGbIzaifA@public.gmane.org>
2010-06-16 17:24   ` Martin Peres [this message]
     [not found]     ` <4C1908B3.2060201-Iz16wY1oaNPLSKGbIzaifA@public.gmane.org>
2010-06-17 19:36       ` Stephane Marchesin
     [not found]         ` <AANLkTin383_xfgGamabXVUHaE2DA7pG5wLNa7VW574Ob-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-06-17 19:49           ` Martin Peres

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=4C1908B3.2060201@ensi-bourges.fr \
    --to=martin.peres-iz16wy1oanplskgbizaifa@public.gmane.org \
    --cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.