linux-kernel - Enhanced reimplemention of the kfifo API request for merge

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

Message-ID: <1266572356.10556.13.camel@wall-e>
Date:	Fri, 19 Feb 2010 10:39:16 +0100
From:	Stefani Seibold <stefani@...bold.net>
To:	linux-kernel <linux-kernel@...r.kernel.org>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	Andi Kleen <andi@...stfloor.org>,
	Greg Kroah-Hartman <gregkh@...e.de>,
	Alan Cox <alan@...rguk.ukuu.org.uk>,
	Theodore Tso <tytso@....edu>,
	"Ira W. Snyder" <iws@...o.caltech.edu>,
	Linus Torvalds <torvalds@...l.org>
Subject: Enhanced reimplemention of the kfifo API request for merge

Hi,

is there a change to get the new generic kfifo API merged into the
linux-next, mm- or the upcoming 2.6.34 tree?

All features and complains are implemented. I got a lot of commits and
positve feedback but no ack's.

So the question is should i continue to work?

If i get an okay for the merge, the next steps will be:

- add a short HOWTO file into the Documentation directory
- replace all kfifo_out_locked() into kfifo_out_spinlocked() and
  replace all kfifo_in_locked() into kfifo_in_spinlocked()
- modify the drivers to use the type based FIFO
- maybe port drivers which use its own fifo implementation to the new
  kfifo API

Stefani ;-)


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