mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andy Walls <awalls@radix.net>
To: Stefani Seibold <stefani@seibold.net>
Cc: Andi Kleen <andi@firstfloor.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Arnd Bergmann <arnd@arndb.de>,
	Amerigo Wang <xiyou.wangcong@gmail.com>,
	Joe Perches <joe@perches.com>,
	linux-media@vger.kernel.org,
	Mauro Carvalho Chehab <mchehab@infradead.org>
Subject: Re: [PATCH 0/7] kfifo: new API v0.6
Date: Tue, 27 Oct 2009 21:49:31 -0400	[thread overview]
Message-ID: <1256694571.3131.26.camel@palomino.walls.org> (raw)


> One thing is that the new API is not compatible with the old one. I
> had a look at the current user of the old kfifo API and it is was easy
> to adapt it to the new API. These are the files which currently use
> the kfifo API:
> 
> drivers/char/nozomi.c
> drivers/char/sonypi.c
> drivers/infiniband/hw/cxgb3/cxio_resource.c
> drivers/media/video/meye.c
> drivers/net/wireless/libertas/main.c
> drivers/platform/x86/fujitsu-laptop.c
> drivers/platform/x86/sony-laptop.c
> drivers/scsi/libiscsi.c
> drivers/scsi/libiscsi_tcp.c
> drivers/scsi/libsrp.c
> drivers/usb/host/fhci.h
> net/dccp/probe.c
> drivers/usb/serial/usb-serial.c
> drivers/usb/serial/generic.c

Here's a V4L-DVB cx23885 module change, that is on its way upstream,
that uses kfifo as is:

http://linuxtv.org/hg/v4l-dvb/rev/a2d8d3d88c6d

Do you really have to break the old API?

Regards,
Andy


             reply	other threads:[~2009-10-28  1:47 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-28  1:49 Andy Walls [this message]
2009-10-28  3:20 ` Andi Kleen
2009-10-28  5:36   ` Mauro Carvalho Chehab
  -- strict thread matches above, loose matches on Subject: below --
2009-11-16 11:50 Stefani Seibold
2009-11-18 21:33 ` Andrew Morton
2009-10-24 13:33 Stefani Seibold
2009-10-25  1:48 ` Andi Kleen
2009-10-25  8:12   ` Stefani Seibold
2009-10-30 22:24 ` Greg KH
2009-10-31  7:50   ` Stefani Seibold
2009-10-31 19:10     ` Greg KH
2009-11-01  9:50       ` Stefani Seibold

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=1256694571.3131.26.camel@palomino.walls.org \
    --to=awalls@radix.net \
    --cc=akpm@linux-foundation.org \
    --cc=andi@firstfloor.org \
    --cc=arnd@arndb.de \
    --cc=joe@perches.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@infradead.org \
    --cc=stefani@seibold.net \
    --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
all inboxes | Powered by JetHome®