Re: [PATCH 0/3] New firewire stack

> One thing is for sure, the fw_ prefix is not too well suited to stay
> if/when Kristian's code is pushed to mainline. During a switch period,
> we could e.g. replace the old stack's prefixes by hpsb1_ (as the 1st
> generation of FireWire kernel APIs) or whatever and replace Kristian's
> prefixes by hpsb_. I would actually like fw_ most (if it wasn't so
> overloaded and already used in other contexts) and the author's decision
> should be honored too.

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

Ben.


-
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/

Follow-Ups:
- Re: [PATCH 0/3] New firewire stack
  - From: Stefan Richter <[email protected]>

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]>

Prev by Date: Re: [NETLINK]: Schedule removal of old macros exported to userspace
Next by Date: Re: [PATCH] kcalloc: Re-order the first two out-of-order args to kcalloc().
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]