linux-arch.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chris Metcalf <cmetcalf@tilera.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Matthew Wilcox <matthew@wil.cx>,
	linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org
Subject: Re: [PATCH] Break out types from <linux/list.h> to <linux/list_types.h>.
Date: Sat, 3 Jul 2010 21:47:58 -0400	[thread overview]
Message-ID: <4C2FE84E.4010407@tilera.com> (raw)
In-Reply-To: <201007031100.43158.arnd@arndb.de>

On 7/3/2010 5:00 AM, Arnd Bergmann wrote:
> On Friday 02 July 2010 22:48:17 Matthew Wilcox wrote:
>   
>> I wouldn't mind seeing kvm_types.h, rwlock_types.h and spinlock_types.h
>> merged into types.h, personally.  They're all pretty fundamental kernel
>> kind of types.  It's a matter of taste, and I'm not particularly fussed
>> one way or the other.
>>
>> mm_types.h is complex and full of mm-specific information, so keeping
>> it separate makes sense to me.
>>
>> I just object to the unnecessary creation of tiny files like this.
>> Which is how we ended up with atomic_t and atomic64_t in there in the
>> first place :-)
>>     
> Ah, I didn't notice you had moved the atomic types in there. I agree that
> the list types are in the same general category and it makes sense
> to treat them the same way.
>
> For rwlock_types.h and spinlock_types.h, I think including them in types.h
> would really cause too much other crap to be pulled in through lockdep
> and other things we might need in there in the future, which would in turn
> cause the same problems with types.h that Chris is trying to avoid
> in the first place by moving stuff out of list.h.
>   

Sounds like we have a consensus on moving the list_head, hlist_head, and
hlist_node types to <linux/types.h>.  I assume everyone is agreed that
initializers, etc., should stay in <linux/list.h>.  I will send out a
revised git patch on Sunday.

-- 
Chris Metcalf, Tilera Corp.
http://www.tilera.com

  reply	other threads:[~2010-07-04  1:48 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <201006252110.o5PLArvw010770@farm-0002.internal.tilera.com>
     [not found] ` <201006281312.16391.arnd@arndb.de>
     [not found]   ` <4C28BE64.4050505@tilera.com>
2010-06-28 19:34     ` [PATCH] arch/tile: Add driver to enable access to the user dynamic network Arnd Bergmann
2010-07-02 12:19       ` Chris Metcalf
2010-07-02 16:11         ` Arnd Bergmann
2010-07-02 17:41           ` [PATCH] Break out types from <linux/list.h> to <linux/list_types.h> Chris Metcalf
2010-07-02 19:19             ` Matthew Wilcox
2010-07-02 19:33               ` Chris Metcalf
2010-07-02 20:48                 ` Matthew Wilcox
2010-07-02 21:09                   ` Chris Metcalf
2010-07-03  8:44                   ` Alexey Dobriyan
2010-07-03  9:00                   ` Arnd Bergmann
2010-07-04  1:47                     ` Chris Metcalf [this message]
2010-07-04  3:22                       ` Matthew Wilcox
2010-07-02 20:43               ` Arnd Bergmann
2010-07-02 21:10                 ` Christoph Hellwig
2010-07-02 17:52           ` [PATCH] arch/tile: Add driver to enable access to the user dynamic network Chris Metcalf

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4C2FE84E.4010407@tilera.com \
    --to=cmetcalf@tilera.com \
    --cc=arnd@arndb.de \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matthew@wil.cx \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).