* Martin Schwidefsky <schwidefsky@de.ibm.com> wrote:yes, you are right and your fix is the correct one. Currently, if we define GENERIC_LOCKBREAK on UP then we get accesses to the non-existing lock->need_lockbreak field. [ btw., this is really a small uncleanliness in the generic code: it should be possible for an architecture to just enable GENERIC_LOCKBREAK unconditionally, to indicate that it intends to "let the generic code do this". Then the generic code, when it does not have a field (such as on UP), should just not access it. But this is a small detail. ] Ingo --
| Andrew Morton | -mm merge plans for 2.6.23 |
| david | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Linus Torvalds | Linux 2.6.27-rc5 |
| Bart Van Assche | Integration of SCST in the mainstream Linux kernel |
git: | |
| David Miller | Re: [GIT]: Networking |
| Gerrit Renker | [PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side) |
| Jarek Poplawski | [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Lennert Buytenhek | [PATCH 16/39] mv643xx_eth: get rid of ETH_/ethernet_/eth_ prefixes |
