From: Stefani Seibold <stefani@seibold.net>
To: linux-kernel <linux-kernel@vger.kernel.org>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>, Theodore Tso <tytso@mit.edu>,
Andrew Morton <akpm@linux-foundation.org>,
Arnd Bergmann <arnd@arndb.de>, Andi Kleen <andi@firstfloor.org>,
Amerigo Wang <xiyou.wangcong@gmail.com>,
Joe Perches <joe@perches.com>,
Roger Quadros <quadros.roger@gmail.com>,
"Ira W. Snyder" <iws@ovro.caltech.edu>,
Greg Kroah-Hartman <gregkh@suse.de>,
Mauro Carvalho Chehab <mchehab@redhat.com>,
Shargorodsky Atal <ext-atal.shargorodsky@nokia.com>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Merge of the enhanced reimplemention of the kfifo API
Date: Wed, 03 Feb 2010 18:46:58 +0100 [thread overview]
Message-ID: <1265219218.22285.21.camel@wall-e> (raw)
Hi,
-rc6 is out and i ask for merging the new macro based kfifo
reimplementation into linux-next and/or 2.6.34. I got a lot of positive
feedback but currently no ACK.
The reimplementation is 100% compatible to the previous one but more
flexibel and highly optimized. The code is tested and works fine.
I am sorry about the size of the patch, but there is no way to split it
down into separate patches because it is a complete different approach
and a full replacement of the kfifo.c and kfifo.h files.
You can access the latest posting at
http://patchwork.kernel.org/patch/75443/
If i get an okay, i will fix the current users of the kfifo from using
byte stream fifo to the desired data type. Maybe with the help of
Greg ;-)
I hate to write code for the trash bin, so please give it a try.
Greetings,
Stefani
BTW: Zack Brown wrote a positive statement in the German Linux magazine.
reply other threads:[~2010-02-03 17:47 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1265219218.22285.21.camel@wall-e \
--to=stefani@seibold.net \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=andi@firstfloor.org \
--cc=arnd@arndb.de \
--cc=dmitry.torokhov@gmail.com \
--cc=ext-atal.shargorodsky@nokia.com \
--cc=gregkh@suse.de \
--cc=iws@ovro.caltech.edu \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@redhat.com \
--cc=quadros.roger@gmail.com \
--cc=torvalds@linux-foundation.org \
--cc=tytso@mit.edu \
--cc=xiyou.wangcong@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox