From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753167Ab0F1TfF (ORCPT ); Mon, 28 Jun 2010 15:35:05 -0400 Received: from moutng.kundenserver.de ([212.227.126.187]:52032 "EHLO moutng.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751348Ab0F1TfB (ORCPT ); Mon, 28 Jun 2010 15:35:01 -0400 From: Arnd Bergmann To: Chris Metcalf Subject: Re: [PATCH] arch/tile: Add driver to enable access to the user dynamic network. Date: Mon, 28 Jun 2010 21:34:55 +0200 User-Agent: KMail/1.13.3 (Linux/2.6.35-rc3-00069-gc502b38-dirty; KDE/4.4.85; x86_64; ; ) Cc: linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org References: <201006252110.o5PLArvw010770@farm-0002.internal.tilera.com> <201006281312.16391.arnd@arndb.de> <4C28BE64.4050505@tilera.com> In-Reply-To: <4C28BE64.4050505@tilera.com> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Message-Id: <201006282134.55166.arnd@arndb.de> X-Provags-ID: V01U2FsdGVkX1+l8WEvLSXBsULtDvoUHQ9GhJNPhVIyfV5M6qR mP6vDxl7xsPYMjeOl4xt1wo5qT0dWucY229tWt4txEvojpgu7A L0gso6lM8L+80PLWRAdOg== Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Cc'ing linux-arch on the question of how to use a list_head in processor.h. On Monday 28 June 2010 17:23:16 Chris Metcalf wrote: > > We could break the dependency by turning prefetch_range into a macro > > or an extern function. There is only one user, and it's in a staging > > driver, so the impact would be minimal. > > > > I don't think so. The problem is that users of expect to > be able to #include that one header, then use things like > list_for_each() (which uses prefetch, as defined in ), > but without also being required to #include themselves > explicitly. Right. > I think the only "true" fix would be to have a new > header that provides list_head (and presumably hlist_head and > hlist_node), which would include, as would our > . This is certainly in line with recent > header-separation changes (e.g. mm_types.h). Would there be interest in > a change like this? I implemented it in my tree, and if it sounds > plausible to you, I'll send out a git diff, but it looks pretty much > exactly like this description :-) Yes, I think that would be a reasonable change. Another alternative might be to move the prefetch stuff from asm/processor.h to asm/prefetch.h on all architectures, which also breaks the dependency loop, unless I'm mistaken again. Arnd