lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Message-ID: <CACRpkdbZWMk9+wH8ndFEzZyUwKecjNfgT2xJnZEQx0ACPzLWbw@mail.gmail.com> Date: Mon, 3 Oct 2022 20:54:31 +0200 From: Linus Walleij <linus.walleij@...aro.org> To: Khalid Masum <khalid.masum.92@...il.com> Cc: David Airlie <airlied@...ux.ie>, Daniel Vetter <daniel@...ll.ch>, dri-devel@...ts.freedesktop.org, linux-kernel@...r.kernel.org Subject: Re: [PATCH] drm/tve200: Use drm_* variants for logging On Wed, Sep 28, 2022 at 11:31 AM Khalid Masum <khalid.masum.92@...il.com> wrote: > We have routines like drm_info/warn/err for logging. Use them instead > of dev_* variants to get drm-formatted log messages. > > Signed-off-by: Khalid Masum <khalid.masum.92@...il.com> So is this the new thing? We've been through: - DRM_INFO_ETC BIG CAPITAL LETTER MACROS - Just use dev_info() & friends like everyone else - Now drm_info() & co Note I don't wanna bikeshed about this, just tell me there is consensus now so we know what to do. Yours, Linus Walleij
Powered by blists - more mailing lists