From: Jani Nikula <jani.nikula@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH v2] drm/i915: clarify logging about reasons for disabling FBC
Date: Tue, 19 Feb 2013 12:00:11 +0200 [thread overview]
Message-ID: <87sj4spqs4.fsf@intel.com> (raw)
In-Reply-To: <20130219092019.GB4683@cantiga.alporthouse.com>
On Tue, 19 Feb 2013, Chris Wilson <chris@chris-wilson.co.uk> wrote:
> On Tue, Feb 19, 2013 at 09:18:20AM +0200, Jani Nikula wrote:
>> Previously FBC disabling due to per-chip default was logged as being
>> disabled per module parameter. Distinguish between the two.
>>
>> v2: Don't even squawk in the debug log if FBC is explicitly disabled (Chris
>> Wilson).
>
> I'm still not entirely happy, as I still get to see the repeated message
> many time a second, but it is an improvement over the current message.
Right, I was just trying to get rid of printing misleading information
(disabled per module parameter when it was the per chip default) and
ignored the noise part (which can be more annoying).
Jani.
prev parent reply other threads:[~2013-02-19 9:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-14 11:52 [PATCH] drm/i915: clarify logging about reasons for disabling FBC Jani Nikula
2013-02-14 12:08 ` Chris Wilson
2013-02-19 7:18 ` [PATCH v2] " Jani Nikula
2013-02-19 9:20 ` Chris Wilson
2013-02-19 10:00 ` Jani Nikula [this message]
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=87sj4spqs4.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.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.