linux-kernel - Re: [PATCH 1/4] WorkStruct: Separate delayable and non-delayable events.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 21 Nov 2006 11:30:53 +0000
From:	David Howells <dhowells@...hat.com>
To:	Linus Torvalds <torvalds@...l.org>
Cc:	Stefan Richter <stefanr@...6.in-berlin.de>,
	David Howells <dhowells@...hat.com>, akpm@...l.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/4] WorkStruct: Separate delayable and non-delayable events. 

Linus Torvalds <torvalds@...l.org> wrote:

> "dwork" just sounds d[w]orky. More importantly, we don't use short-hand 
> that isn't obvious, unless there is some industry-standard and old meaning 
> to it that everybody understands. "delayed_work" may be more typing, but 
> anybody who needs to type things that fast had better slow down anyway to 
> _think_.

Okay...  "delayed_work" it shall be.  Would it make sense to make another
wrapper about the common bit called "immediate_work" and then hide the common
bit entirely?

David
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/