On 12/18/06, Arjan van de Ven <arjan@xxxxxxxxxxxxx> wrote:
> What is the smartest way to update an old patch set to work with a > current kernel version? in my experience (and I've quite a bit of this:) it's essential to do small steps. There are 2 types of small steps 1) small steps in your patch 2) small steps in what you move it to
Thanks for the advice, I will make sure to do that in the future.
Even now that you are where you are, I'd suggest going via at least one, if not two, intermediate steps. Say 2.6.12 and 2.6.15. Make those work first, test them a lot, and only then go to the next step. (and going forward, once you are at a current tree, keep up with mainline *frequently*)
I have looked a little into the changes and how they affect our patch. I see your point that the move directly to a current kernel will be very hard and error prone. Unfortunately, I don't have the time right now to do the move(s) (deadlines...), so I have decided to postpone the move to a current version a little more and continue development on the old version. I know that this doesn't help the problem at all, but I can worry about that after I have met my deadline... Thank you very much for your advice! - Bjoern -- Kernelnewbies: Help each other learn about the Linux kernel. Archive: http://mail.nl.linux.org/kernelnewbies/ FAQ: http://kernelnewbies.org/faq/
