Re: Where did vm_operations_struct->unmap in 2.4.0 go?

From: David Woodhouse (dwmw2@infradead.org)
Date: Mon Jan 15 2001 - 04:09:02 EST

Next message: fool@elven.org: "linux-2.4.0: couple typos in 'make menuconfig', also kbd freeze workaround, stuck swapping, etc"
Previous message: Christoph Rohland: "[Patch] memparse should return long long"
In reply to: Keith Owens: "Re: Where did vm_operations_struct->unmap in 2.4.0 go?"
Next in thread: Christian Zander: "Re: Where did vm_operations_struct->unmap in 2.4.0 go?"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

kaos@ocs.com.au said:
> That is a lot of work for a very few special cases. OTOH, you could
> just add a few lines of __initcall code in two source files (which I
> did when I wrote inter_module_xxx) and swap the order of 3 lines in
> drivers/mtd/Makefile. Guess which alternative I am going for?

I've already worked round it for the 2.[024] case by reintroducing the
ifdefs. I assume here that we're planning for 2.5. As part of the many
changes that are going to be introduced during 2.5, this shouldn't be too
intrusive.

Once it's actually usable for the common case, it won't just be 'a very few
special cases' any more. But that's all 2.5 material.

-- dwmw2

- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org Please read the FAQ at http://www.tux.org/lkml/

Next message: fool@elven.org: "linux-2.4.0: couple typos in 'make menuconfig', also kbd freeze workaround, stuck swapping, etc"
Previous message: Christoph Rohland: "[Patch] memparse should return long long"
In reply to: Keith Owens: "Re: Where did vm_operations_struct->unmap in 2.4.0 go?"
Next in thread: Christian Zander: "Re: Where did vm_operations_struct->unmap in 2.4.0 go?"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Mon Jan 15 2001 - 21:00:40 EST