Searched hist:de5d9bf6 (Results 1 - 2 of 2) sorted by relevance
| /linux-master/include/linux/ | ||
| H A D | types.h | diff de5d9bf6 Fri Jul 02 11:41:14 MDT 2010 Chris Metcalf <cmetcalf@tilera.com> Move list types from <linux/list.h> to <linux/types.h>. This allows a list_head (or hlist_head, etc.) to be used from places that used to be impractical, in particular <asm/processor.h>, which used to cause include file recursion: <linux/list.h> includes <linux/prefetch.h>, which always includes <asm/processor.h> for the prefetch macros, as well as <asm/system.h>, which often includes <asm/processor.h> directly or indirectly. This avoids a lot of painful workaround hackery on the tile architecture, where we use a list_head in the thread_struct to chain together tasks that are activated on a particular hardwall. Signed-off-by: Chris Metcalf <cmetcalf@tilera.com> Reviewed-by: Matthew Wilcox <willy@linux.intel.com> |
| H A D | list.h | diff de5d9bf6 Fri Jul 02 11:41:14 MDT 2010 Chris Metcalf <cmetcalf@tilera.com> Move list types from <linux/list.h> to <linux/types.h>. This allows a list_head (or hlist_head, etc.) to be used from places that used to be impractical, in particular <asm/processor.h>, which used to cause include file recursion: <linux/list.h> includes <linux/prefetch.h>, which always includes <asm/processor.h> for the prefetch macros, as well as <asm/system.h>, which often includes <asm/processor.h> directly or indirectly. This avoids a lot of painful workaround hackery on the tile architecture, where we use a list_head in the thread_struct to chain together tasks that are activated on a particular hardwall. Signed-off-by: Chris Metcalf <cmetcalf@tilera.com> Reviewed-by: Matthew Wilcox <willy@linux.intel.com> |
Completed in 170 milliseconds