All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefani Seibold <stefani@seibold.net>
To: linux-kernel <linux-kernel@vger.kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Andi Kleen <andi@firstfloor.org>,
	Greg Kroah-Hartman <gregkh@suse.de>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>, Theodore Tso <tytso@mit.edu>,
	"Ira W. Snyder" <iws@ovro.caltech.edu>,
	Linus Torvalds <torvalds@osdl.org>
Subject: Enhanced reimplemention of the kfifo API request for merge
Date: Fri, 19 Feb 2010 10:39:16 +0100	[thread overview]
Message-ID: <1266572356.10556.13.camel@wall-e> (raw)
In-Reply-To: <1265961158.32651.9.camel@wall-e>

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 ;-)



      parent reply	other threads:[~2010-02-19  9:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-12  7:52 [PATCH 0/4] enhanced reimplemention of the kfifo API Stefani Seibold
2010-02-12  7:56 ` [PATCH 1/4] fix kfifo miss use of nozami.c Stefani Seibold
2010-02-12  7:58 ` [PATCH 2/4] remove the old non generic API Stefani Seibold
2010-02-12  8:03 ` [PATCH 3/4] add the new generic kfifo API Stefani Seibold
2010-02-12  8:07 ` [PATCH 4/4] add example files to the kernel sample directory Stefani Seibold
2010-02-19  9:39 ` Stefani Seibold [this message]

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=1266572356.10556.13.camel@wall-e \
    --to=stefani@seibold.net \
    --cc=akpm@linux-foundation.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=andi@firstfloor.org \
    --cc=gregkh@suse.de \
    --cc=iws@ovro.caltech.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.org \
    --cc=tytso@mit.edu \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.