From: "Christian König" <christian.koenig@amd.com> To: Suraj Upadhyay <usuraj35@gmail.com>, alexander.deucher@amd.com Cc: amd-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org Subject: Re: [Proposal] DRM: AMD: Convert logging to drm_* functions. Date: Thu, 9 Jul 2020 09:14:15 +0200 [thread overview] Message-ID: <e5389684-424e-6a38-37d8-9910cdb8b2f3@amd.com> (raw) In-Reply-To: <20200708161123.GA30962@blackclown> Am 08.07.20 um 18:11 schrieb Suraj Upadhyay: > Hii AMD Maintainers, > I plan to convert logging of information, error and warnings > inside the AMD driver(s) to drm_* functions and macros for loggin, > as described by the TODO list in the DRM documentation[1]. > > I need your approval for the change before sending any patches, to make > sure that this is a good idea and that the patches will be merged. > > The patches will essentially convert all the dev_info(), dev_warn(), > dev_err() and dev_err_once() to drm_info(), drm_warn(), drm_err() and > drm_err_once() respectively. Well to be honest I would rather like see the conversion done in the other direction. I think the drm_* functions are just an unnecessary extra layer on top of the core kernel functions and should probably be removed sooner or later because of midlayering. Regards, Christian. > > Thank You, > > Suraj Upadhyay. > > [1] https://dri.freedesktop.org/docs/drm/gpu/todo.html#convert-logging-to-drm-functions-with-drm-device-paramater >
WARNING: multiple messages have this Message-ID (diff)
From: "Christian König" <christian.koenig@amd.com> To: Suraj Upadhyay <usuraj35@gmail.com>, alexander.deucher@amd.com Cc: linux-kernel@vger.kernel.org, amd-gfx@lists.freedesktop.org Subject: Re: [Proposal] DRM: AMD: Convert logging to drm_* functions. Date: Thu, 9 Jul 2020 09:14:15 +0200 [thread overview] Message-ID: <e5389684-424e-6a38-37d8-9910cdb8b2f3@amd.com> (raw) In-Reply-To: <20200708161123.GA30962@blackclown> Am 08.07.20 um 18:11 schrieb Suraj Upadhyay: > Hii AMD Maintainers, > I plan to convert logging of information, error and warnings > inside the AMD driver(s) to drm_* functions and macros for loggin, > as described by the TODO list in the DRM documentation[1]. > > I need your approval for the change before sending any patches, to make > sure that this is a good idea and that the patches will be merged. > > The patches will essentially convert all the dev_info(), dev_warn(), > dev_err() and dev_err_once() to drm_info(), drm_warn(), drm_err() and > drm_err_once() respectively. Well to be honest I would rather like see the conversion done in the other direction. I think the drm_* functions are just an unnecessary extra layer on top of the core kernel functions and should probably be removed sooner or later because of midlayering. Regards, Christian. > > Thank You, > > Suraj Upadhyay. > > [1] https://dri.freedesktop.org/docs/drm/gpu/todo.html#convert-logging-to-drm-functions-with-drm-device-paramater > _______________________________________________ amd-gfx mailing list amd-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/amd-gfx
next prev parent reply other threads:[~2020-07-09 7:14 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-07-08 16:11 [Proposal] DRM: AMD: Convert logging to drm_* functions Suraj Upadhyay 2020-07-08 16:11 ` Suraj Upadhyay 2020-07-09 7:14 ` Christian König [this message] 2020-07-09 7:14 ` Christian König
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=e5389684-424e-6a38-37d8-9910cdb8b2f3@amd.com \ --to=christian.koenig@amd.com \ --cc=alexander.deucher@amd.com \ --cc=amd-gfx@lists.freedesktop.org \ --cc=linux-kernel@vger.kernel.org \ --cc=usuraj35@gmail.com \ /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: linkBe 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.