linux-kernel - [PATCH] drm: Remove DRIVER_DATE and CORE

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <AANLkTi=nE87vGVvYQQgAjYXBRZtcq=j5Do1S47WQFLt1@mail.gmail.com>
Date:	Wed, 22 Dec 2010 10:51:26 +0100
From:	Sedat Dilek <sedat.dilek@...glemail.com>
To:	Dave Airlie <airlied@...il.com>
Cc:	linux-next@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>,
	DRI <dri-devel@...ts.freedesktop.org>,
	Michel Dänzer <michel@...nzer.net>
Subject: [PATCH] drm: Remove DRIVER_DATE and CORE_DATE

DRIVER_DATE is not maintained or upgraded on changes in many drm drivers.

For example radeon has one DRIVER_DATE for User and Kernel ModeSetting
driver, this makes no sense as UMS and KMS driver have different versions.
And of course this all increases maintenance, too.
For radeon it is enough to bump {KMS_}DRIVER_MAJOR, {KMS_}DRIVER_MINOR and
{KMS_}DRIVER_PATCHLEVEL defines.

Furthermore, I also removed CORE_DATE.

With radeon-KMS my dmesg looks now like this:

[   12.328937] [drm] Initialized drm 1.1.0
[   13.144019] [drm] Initialized radeon 2.8.0 for 0000:01:00.0 on minor 0

Signed-off-by: Sedat Dilek <sedat.dilek@...il.com>

Note: Tested with radeon RV250 (KMS) and linux-next (next-20101221).

Download attachment "0001-drm-Remove-DRIVER_DATE-and-CORE_DATE.patch" of type "plain/text" (14544 bytes)