From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Nathan Lynch <nathanl@austin.ibm.com>
Cc: linuxppc-dev list <linuxppc-dev@lists.linuxppc.org>
Subject: Re: [PATCH/RFC] add proc_dir_entry fields to device_node
Date: Mon, 06 Oct 2003 21:40:26 +0200 [thread overview]
Message-ID: <1065469225.30245.5.camel@gaston> (raw)
In-Reply-To: <3F81BEA6.50908@austin.ibm.com>
> while the ppc versions are no-ops. This would preserve source
> compatibility while keeping us from breaking BootX.
>
> Separate patches against kernel.org 2.6.0-test6 attached.
go on. I don't have much time to work on this right now. I hope
I'll be able to move us away from BootX format later this year
Ben.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2003-10-06 19:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-03 16:22 [PATCH/RFC] add proc_dir_entry fields to device_node Nathan Lynch
2003-10-04 7:55 ` Benjamin Herrenschmidt
2003-10-06 19:12 ` Nathan Lynch
2003-10-06 19:40 ` Benjamin Herrenschmidt [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=1065469225.30245.5.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=nathanl@austin.ibm.com \
/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).