From: Dave Airlie <airlied@gmail.com>
To: Jerome Glisse <glisse@freedesktop.org>
Cc: dri-devel@lists.sf.net
Subject: Re: Convert DRM_INFO/DRM_ERROR to dev_info/dev_err
Date: Mon, 1 Mar 2010 15:47:35 +1000 [thread overview]
Message-ID: <21d7e9971002282147g3c5d1e96g4e65cbf7aefd3d58@mail.gmail.com> (raw)
In-Reply-To: <20100225185649.GA1981@barney.localdomain>
On Fri, Feb 26, 2010 at 4:56 AM, Jerome Glisse <glisse@freedesktop.org> wrote:
> Attached is conversion from DRM_INFO/DRM_ERROR to dev_info/dev_err
> to apply it copy all doconv* file into the radeon subfolder of the
> kernel run ./doconv.sh and then apply the 0001 patch which fix
> compilation after conversion (place where struct radeon_device is
> missing) then thing should compile
>
> I think it's worthwhile cleanup especialy on multi GPU configuration.
Does this not remove the drm log levels?
so we end up with everything in dmesg the whole time?
that seems wrong, I'd rather pass a dev to DRM_ERROR/DRM_INFO
or maybe defined DRM_DEV_ERROR, DRM_DEV_INFO.
Dave.
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
--
next prev parent reply other threads:[~2010-03-01 5:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-25 18:56 Convert DRM_INFO/DRM_ERROR to dev_info/dev_err Jerome Glisse
2010-03-01 5:47 ` Dave Airlie [this message]
2010-03-01 11:46 ` Jerome Glisse
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=21d7e9971002282147g3c5d1e96g4e65cbf7aefd3d58@mail.gmail.com \
--to=airlied@gmail.com \
--cc=dri-devel@lists.sf.net \
--cc=glisse@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.