linux-kernel - [PATCH 0/8] Homogenize application output and fix sparse warnings.

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>] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 18 Jun 2012 13:11:58 +0200
From:	Miguel Gómez <magomez@...lia.com>
To:	arnaud.patard@...-net.org, gregkh@...uxfoundation.org,
	aaro.koskinen@....fi, dan.carpenter@...cle.com
Cc:	devel@...verdev.osuosl.org, linux-kernel@...r.kernel.org,
	Miguel Gómez <magomez@...lia.com>
Subject: [PATCH 0/8] Homogenize application output and fix sparse warnings.

This serie of patches mailnly try to homogenize module's output by removing some
custom macros and printk calls, and using pr_* and dev_* functions instead.
Also, they fix the definition of a fuction only in debug mode and fix some
sparse warnings.

Miguel Gómez (8):
  Staging: xgifb: reformat module parameter descriptions.
  Staging: xgifb: remove DEBUGPRN() macro and its uses.
  Staging: xgifb: remove DPRINTK() macro and replace it with pr_debug.
  Staging: xgifb: define real dumpVGAReg() content only in DEBUG mode.
  Staging: xgifb: Remove XGIFAIL() macro and its calls.
  Staging: xgifb: Remove printk usage.
  Staging: xgifb: Fix sparse warnings.
  Staging: xgifb: Replace pr_* with dev_* when possible.

 drivers/staging/xgifb/XGI_main.h    |    2 -
 drivers/staging/xgifb/XGI_main_26.c |  189 ++++++++++++++++-------------------
 drivers/staging/xgifb/vb_init.c     |   48 +--------
 drivers/staging/xgifb/vb_setmode.c  |    2 +-
 drivers/staging/xgifb/vb_util.c     |    1 +
 5 files changed, 92 insertions(+), 150 deletions(-)

-- 
1.7.9.5

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/