Christian Gennerat a �crit :
>
> It is a big job.
> But it would be better if the kernel source kept a trace of all changes.
> could you add a "irda/Changelog" file where will be logged
> all patches incorporated in the source.
You will notice that I've got an habit of commenting
extensively my patches *inside* the patch, at the place of the
change. In fact, I would not be surprise if 90% of the meaningful
comments in the IrDA stack are mine.
The changelog has been posted on the linux-irda mailing
list. You can find it forever in the archive :
http://www.pasta.cs.uit.no/pipermail/linux-irda/2001-September/003132.html
> will the next 2.4.10 irda stack be patch free ?
> or are there some pending patches ?
All *my* patches are in the kernel. Note that those patches
fix mostly rarely used features and corner cases, so 99% of the people
won't see the difference. The only thing that people may notice is the
fix for the socket memory leak. In other words : 2.4.9 works (as far
as IrDA is concerned).
For other patches, I've no idea. I believe that there is no
outstanding patch for the IrDA stack, just outstanding bug (skbuff
memory leak, ...). IrDA is a *small* part of my activities and
decreasing, so I tend to fix only the things getting on my way.
I know that Martin Diehl has a patch for the VLSI driver and
that Benjamin Kong has a patch for the ALI driver. Shimizu Takuya has
done a driver for the Actisys 200L dongle. I don't have those
hardware, so I can't comment on the quality of their work, and I
prefer them to be responsible for their own work. If they want to send
those patches directly to me, I can forward them to Linus, but I won't
be able to do more than that.
That's it...
Jean
_______________________________________________
Linux-IrDA mailing list - [EMAIL PROTECTED]
http://www.pasta.cs.UiT.No/mailman/listinfo/linux-irda
