public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <andi@firstfloor.org>
To: Greg KH <gregkh@suse.de>
Cc: Stefani Seibold <stefani@seibold.net>,
	linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
	"Ira W. Snyder" <iws@ovro.caltech.edu>,
	Andi Kleen <andi@firstfloor.org>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>,
	tytso@mit.edu
Subject: Re: new gerneric kfifo API
Date: Thu, 5 Aug 2010 11:04:24 +0200	[thread overview]
Message-ID: <20100805090424.GD29966@basil.fritz.box> (raw)
In-Reply-To: <20100804194617.GA30773@suse.de>

On Wed, Aug 04, 2010 at 12:46:17PM -0700, Greg KH wrote:
> On Wed, Aug 04, 2010 at 09:10:54AM +0200, Stefani Seibold wrote:
> > Hi,
> > 
> > once again. Kernel 2.6.35 is out and i want to know if there is play plan to
> > merge the generic kfifo API. All complains was fixed, so there is no
> > reason to shift the merge again. Please gibe me a short answer.
> 
> These have been in the -mm tree for a few major kernel releases now,
> right?  And they are API safe, and only change the internals, right?

I thought they changed the API. But generally to the better.

The newer version seemed ok to me last time I looked.
The older version it replaced had some issues.

-Andi
-- 
ak@linux.intel.com -- Speaking for myself only.

      parent reply	other threads:[~2010-08-05  9:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <201005132135.o4DLZ9WI021613@imap1.linux-foundation.org>
2010-08-04  7:10 ` new gerneric kfifo API Stefani Seibold
2010-08-04  7:16   ` Andrew Morton
2010-08-04 19:46   ` Greg KH
2010-08-04 20:09     ` Stefani Seibold
2010-08-04 20:17       ` Greg KH
2010-08-04 21:52         ` Andrew Morton
2010-08-04 22:02           ` stefani
2010-08-04 23:01             ` Ira W. Snyder
2010-08-05  9:04     ` Andi Kleen [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=20100805090424.GD29966@basil.fritz.box \
    --to=andi@firstfloor.org \
    --cc=akpm@linux-foundation.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=gregkh@suse.de \
    --cc=iws@ovro.caltech.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stefani@seibold.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox