From: "Kristian Høgsberg" <krh@bitplanet.net>
To: "Stefan Richter" <stefanr@s5r6.in-berlin.de>
Cc: linux1394-user@lists.sourceforge.net,
"Kristian Høgsberg" <krh@redhat.com>,
linux1394-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: [rfc patch] firewire: prefix modules with firewire- instead of fw-
Date: Fri, 25 May 2007 09:01:30 -0400 [thread overview]
Message-ID: <59ad55d30705250601wfd344b6od7246a830c3372c3@mail.gmail.com> (raw)
In-Reply-To: <tkrat.68cdceb78a7f6e10@s5r6.in-berlin.de>
On 5/25/07, Stefan Richter <stefanr@s5r6.in-berlin.de> wrote:
> Of course everybody immediately associates "fw-" with FireWire, not
> firmware or firewall or whatever. But "firewire-" has a nice ring to
> it too.
It's fine with me. I like the less ambiguous names better, and I
don't think the length of the names is a problem. If you end up
typing the module names too much, you're doing something wrong or
working on the firewire stack, in which case you're screwed anyway :)
Kristian
prev parent reply other threads:[~2007-05-25 13:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-25 11:54 Stefan Richter
2007-05-25 13:01 ` Kristian Høgsberg [this message]
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=59ad55d30705250601wfd344b6od7246a830c3372c3@mail.gmail.com \
--to=krh@bitplanet.net \
--cc=krh@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux1394-devel@lists.sourceforge.net \
--cc=linux1394-user@lists.sourceforge.net \
--cc=stefanr@s5r6.in-berlin.de \
/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
all inboxes | Powered by JetHome®