Re: [PATCH 0/3] New firewire stack

Benjamin Herrenschmidt wrote:
> One of the problems with hpsb_ is that it's a total pain to type
> and doesn't mean anything at first sight :-)

Both prevent that other people snatch this prefix from us. Also, only
people who can recite the meaning of that acronym when asleep are
permitted to call hpsb_ functions in their code. :-)
-- 
Stefan Richter
-=====-=-==- ==-- -=--=
http://arcgraph.de/sr/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

References:
- [PATCH 0/3] New firewire stack
  - From: "Kristian Høgsberg" <[email protected]>
- Re: [PATCH 0/3] New firewire stack
  - From: Marcel Holtmann <[email protected]>
- Re: [PATCH 0/3] New firewire stack
  - From: Kristian Høgsberg <[email protected]>
- Re: [PATCH 0/3] New firewire stack
  - From: Erik Mouw <[email protected]>
- Re: [PATCH 0/3] New firewire stack
  - From: Pavel Machek <[email protected]>
- Re: [PATCH 0/3] New firewire stack
  - From: Stefan Richter <[email protected]>
- Re: [PATCH 0/3] New firewire stack
  - From: Benjamin Herrenschmidt <[email protected]>

Prev by Date: Re: [patch 08/32] cryptoloop: Select CRYPTO_CBC
Next by Date: Re: sysfs file creation result nightmare (WAS radeonfb: Fix sysfs_create_bin_file warnings)
Previous by thread: Re: [PATCH 0/3] New firewire stack
Next by thread: Re: [PATCH 0/3] New firewire stack
Index(es):
- Date
- Thread

[Index of Archives] [Kernel Newbies] [Netfilter] [Bugtraq] [Photo] [Stuff] [Gimp] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Video 4 Linux] [Linux for the blind] [Linux Resources]