From: David Miller <davem@davemloft.net>
To: jengelh@linux01.gwdg.de
Cc: sparclinux@vger.kernel.org, sfr@canb.auug.org.au,
paulus@samba.org, linuxppc-dev@ozlabs.org
Subject: Re: [PATCH 0/11] Consolidation of Open Firmware routines
Date: Tue, 01 May 2007 01:51:25 -0700 (PDT) [thread overview]
Message-ID: <20070501.015125.93211061.davem@davemloft.net> (raw)
In-Reply-To: <Pine.LNX.4.61.0705011028090.18504@yvahk01.tjqt.qr>
From: Jan Engelhardt <jengelh@linux01.gwdg.de>
Date: Tue, 1 May 2007 10:30:02 +0200 (MEST)
> but i'd kinda want drivers/openfirmware, even if it's a bit longer.
So much for the unix sense of elegance in short names.
I think there is zero confusion about what "of" is.
next prev parent reply other threads:[~2007-05-01 8:51 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-01 7:22 [PATCH 0/11] Consolidation of Open Firmware routines Stephen Rothwell
2007-05-01 7:24 ` [PATCH 01/11] Split out common parts of prom.h Stephen Rothwell
2007-05-01 7:25 ` [PATCH 02/11] Start split out of common open firmware code Stephen Rothwell
2007-05-01 7:26 ` [PATCH 03/11] Consolidate of_device_is_compatible Stephen Rothwell
2007-05-01 7:27 ` [PATCH 04/11] Consolidate of_find_property Stephen Rothwell
2007-05-01 7:28 ` [PATCH 05/11] Consolidate of_get_parent Stephen Rothwell
2007-05-01 7:29 ` [PATCH 06/11] Consolidate of_get_next_child Stephen Rothwell
2007-05-01 7:30 ` [PATCH 07/11] Consolidate of_find_node_by routines Stephen Rothwell
2007-05-01 7:31 ` [PATCH 08/11] Begin to consolidate of_device.c Stephen Rothwell
2007-05-02 1:23 ` Segher Boessenkool
2007-05-01 7:32 ` [PATCH 09/11] Begin consolidation of of_device.h Stephen Rothwell
2007-05-01 7:33 ` [PATCH 10/11] [SPARC/64] Rename some functions like PowerPC Stephen Rothwell
2007-05-01 7:34 ` [PATCH 11/11] Create linux/of_platorm.h Stephen Rothwell
2007-05-01 8:30 ` [PATCH 0/11] Consolidation of Open Firmware routines Jan Engelhardt
2007-05-01 8:51 ` David Miller [this message]
2007-05-01 11:17 ` Jan Engelhardt
2007-05-01 19:36 ` David Miller
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=20070501.015125.93211061.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=jengelh@linux01.gwdg.de \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.org \
--cc=sfr@canb.auug.org.au \
--cc=sparclinux@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).