linux-kernel - [PATCH 0/5] staging:ti dspbridge: Checkpatch errors cleanup series

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:	Wed, 28 Jul 2010 09:40:47 -0500
From:	Ernesto Ramos <ernesto@...com>
To:	gregkh@...e.de
Cc:	omar.ramirez@...com, ohad@...ery.com, ameya.palande@...ia.com,
	felipe.contreras@...ia.com, fernando.lugo@...com,
	linux-kernel@...r.kernel.org, andy.shevchenko@...il.com, nm@...com,
	linux-omap@...r.kernel.org, Ernesto Ramos <ernesto@...com>
Subject: [PATCH 0/5] staging:ti dspbridge: Checkpatch errors cleanup series

These patches are targetted to remove checkpatch errors within
dspbridge driver.

Ernesto Ramos (5):
  staging:ti dspbridge: remove unused typedef REG16
  staging:ti dspbridge: remove unnecessary check for NULL pointer in
    cmm.c
  staging:ti dspbridge: remove function delete_strm_mgr
  staging:ti dspbridge: remove unnecessary volatile variables
  staging:ti dspbridge: replace simple_strtoul by strict_strtoul

 drivers/staging/tidspbridge/core/_tiomap.h    |    2 --
 drivers/staging/tidspbridge/core/tiomap3430.c |    8 ++++----
 drivers/staging/tidspbridge/dynload/tramp.c   |    4 ++--
 drivers/staging/tidspbridge/pmgr/cmm.c        |   15 ++++++---------
 drivers/staging/tidspbridge/rmgr/dbdcd.c      |    6 +++++-
 drivers/staging/tidspbridge/rmgr/strm.c       |   16 ++--------------
 6 files changed, 19 insertions(+), 32 deletions(-)

--
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/