linux-kernel - [PATCH 00/12] SEP cleanups

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, 24 Nov 2010 19:23:46 +0000
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	greg@...ah.com, mark.a.allyn@...el.com,
	linux-kernel@...r.kernel.org
Subject: [PATCH 00/12] SEP cleanups

This is a rework from the bits I sent you a while back Mark (which I suspect
got eaten in the email) and some other cleanup. I've not beaten it up with
CodingStyle yet because most of the debug wants removing before that is done
so it is probably more productive to fix the logic and the inherited choice of
TRUELY_GIANT_DEFINE_NAMES_THAT_CAUSE_MUCH_WRAPPING before we worry about finer
points of style.

---

Alan Cox (12):
      sep: Fix crash if a device is not found
      sep: clean up a couple of spots missed in pass one
      sep: cant is an angular inclination
      sep: Make SEP consistent
      sep: Use kzalloc when needed
      sep: clean up some of the obvious sillies
      sep: Fix the kernel-doc in SEP
      sep: clean up caller_id function
      sep: netlink - what netlink
      sep: handle the memrar stuff in the headers
      sep: handle the rar definition stuff in the header
      sep: minimal fix for wrong include


 drivers/staging/memrar/memrar.h         |   19 
 drivers/staging/sep/sep_driver.c        | 2230 ++++++++++++-------------------
 drivers/staging/sep/sep_driver_config.h |  194 ---
 include/linux/rar_register.h            |   16 
 4 files changed, 902 insertions(+), 1557 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/