From: "Ira W. Snyder" <iws@ovro.caltech.edu>
To: stefani@seibold.net
Cc: Andrew Morton <akpm@linux-foundation.org>,
Greg KH <gregkh@suse.de>,
linux-kernel@vger.kernel.org, Andi Kleen <andi@firstfloor.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
tytso@mit.edu
Subject: Re: new gerneric kfifo API
Date: Wed, 4 Aug 2010 16:01:48 -0700 [thread overview]
Message-ID: <20100804230147.GI23951@ovro.caltech.edu> (raw)
In-Reply-To: <20100805000246.57246lmy2qeimft2@mail.your-server.de>
On Thu, Aug 05, 2010 at 12:02:46AM +0200, stefani@seibold.net wrote:
>
> Zitat von Andrew Morton <akpm@linux-foundation.org>:
>
> > On Wed, 4 Aug 2010 13:17:24 -0700
> > Greg KH <gregkh@suse.de> wrote:
> >
> >> On Wed, Aug 04, 2010 at 10:09:11PM +0200, Stefani Seibold wrote:
> >> > Am Mittwoch, den 04.08.2010, 12:46 -0700 schrieb Greg KH:
> >> > > 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?
> >> > >
> >> > > If so, I see no objection to merging them now, especially as you will be
> >> > > around to fix up any problems that people have, right? :)
> >> > >
> >> >
> >> > right!
> >>
> >> Great. As Andrew doesn't have the time to send them on, want me to? If
> >> so, care to point me at them in his tree, or resend them to me?
> >>
> >
> > One does a little more than "send things on"...
> >
> > I have a little pile of kfifo changes queud for 2.6.36. The "generic
> > kfifo" patches are a large rotorooting of the whole facility, based on
> > that work (I hope).
> >
> > There's also the abandoned
> > kfifo-replace-the-old-non-generic-api-kfifo-fix-scatterlist-usage.patch
> > which never got resolved with the originator.
> >
> >
>
> This patch was included in the latest version i had posted last week.
>
Hello Stefani, Andrew,
I've reviewed the updated patch from Stefani which has incorporated the
fixes I suggested into the DMA routines. The DMA routines have my ack,
though I have not ported any code to them yet.
Thanks,
Ira
next prev parent reply other threads:[~2010-08-04 23:24 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 [this message]
2010-08-05 9:04 ` Andi Kleen
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=20100804230147.GI23951@ovro.caltech.edu \
--to=iws@ovro.caltech.edu \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=andi@firstfloor.org \
--cc=gregkh@suse.de \
--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