On Thu, Oct 29, 2009 at 01:46:40PM -0700, Randy Dunlap wrote:
> On Thu, 29 Oct 2009 01:02:50 +0100 Dominik Brodowski wrote:
>
> > On Wed, Oct 28, 2009 at 10:27:00PM +0100, Dominik Brodowski wrote:
> > > On Tue, Oct 27, 2009 at 07:39:23AM -0700, Greg KH wrote:
> > > > On Tue, Oct 27, 2009 at 06:12:24AM +0100, Dominik Brodowski wrote:
> > > > > Randy,
> > > > >
> > > > > On Mon, Oct 26, 2009 at 03:19:58PM -0700, Randy Dunlap wrote:
> > > > > > > Remove the pcmcia_get_{first,next}_tuple() calls no longer needed by
> > > > > > > (current) pcmcia device drivers.
> > > > > >
> > > > > > linux-next 20091026:
> > > > > >
> > > > > > drivers/staging/comedi/drivers/cb_das16_cs.c:155: error: implicit declaration of function 'pcmcia_get_first_tuple'
> > > > > > drivers/staging/comedi/drivers/cb_das16_cs.c:156: error: implicit declaration of function 'pcmcia_get_tuple_data'
> > > > > > drivers/staging/comedi/drivers/cb_das16_cs.c:883: error: implicit declaration of function 'pcmcia_get_next_tuple'
> > > > > >
> > > > > > There are also other comedi/ drivers that this randconfig didn't attempt
> > > > > > to build that are still using these same interfaces.
> > > > >
> > > > > What are the current rules on drivers in staging/ ? Do they need to be
> > > > > updated as well on API changes?
> > > >
> > > > You don't have to do it, no. I'll be glad to do so as long as I get a
> > > > hint as to what needs to be done :)
> > >
> > > These hints are in Documentation/pcmcia/driver-changes.txt . However, I'll
> > > try to get some patches cooked up myself tonight for those drivers. Whom
> > > shall I submit them to, or shall I just add them to the PCMCIA tree?
> >
> > Update all changes (already those not included in linux-next) which are in
> > the queue for 2.6.33 for all comedi PCMCIA drivers. Compile-tested only, and
> > I'll queue it up with the other PCMCIA patches.
> >
>
> Thanks for the update. What is the patch made against?
2.6.32-rc5 and quite a lot of pcmcia patches which I'll submit for
2.6.33-rc1. Will put it into the repository which "next" pulls from soon.
Best,
Dominik
--
To unsubscribe from this list: send the line "unsubscribe linux-next" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
