Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Tue, 1 Oct 2002 23:18:56 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Tue, 1 Oct 2002 23:18:55 -0400 Received: from TYO202.gate.nec.co.jp ([210.143.35.52]:53916 "EHLO TYO202.gate.nec.co.jp") by vger.kernel.org with ESMTP id ; Tue, 1 Oct 2002 23:18:51 -0400 To: Ingo Molnar Cc: Linus Torvalds , linux-kernel@vger.kernel.org Subject: Re: [patch] Workqueue Abstraction, 2.5.40-H7 References: Reply-To: Miles Bader System-Type: i686-pc-linux-gnu Blat: Foop From: Miles Bader Date: 02 Oct 2002 12:23:42 +0900 In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 703 Lines: 14 Ingo Molnar writes: > then lets at least have 'struct work' and 'struct work_queue' instead of > 'struct work_struct', 'struct work_queue_struct'. "struct work" is already > twice as large as "work_t". I've always wondered about that -- why _does_ linux append `_struct' to some structure names? It seems completely redundant (and ugly). Thanks, -Miles -- The secret to creativity is knowing how to hide your sources. --Albert Einstein - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/