From: Dan Malek <dan@embeddededge.com>
To: John Whitney <johnw@sands-edge.com>
Cc: linuxppc-dev@lists.linuxppc.org, Eugene Surovegin <ebs@ebshome.net>
Subject: Re: Proposed changes to io.h
Date: Wed, 31 Mar 2004 12:40:16 -0500 [thread overview]
Message-ID: <406B0280.1010509@embeddededge.com> (raw)
In-Reply-To: 6D144F40-8339-11D8-9FF0-000A95A07384@sands-edge.com
John Whitney wrote:
> This code specifically handles this .....
OK, already, enough of the e-mails, especially the personal ones. :-P
I was stupid and didn't read the code or comments, just the e-mail
explanation. I don't normally read code unless it is in a patch
that can be compared to something so I can see what has changed.
Thanks.
-- Dan
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-03-31 17:40 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-31 15:44 Proposed changes to io.h John Whitney
2004-03-31 16:44 ` Eugene Surovegin
2004-03-31 16:58 ` Dan Malek
2004-03-31 17:30 ` Matt Porter
2004-03-31 17:32 ` John Whitney
2004-03-31 17:40 ` Dan Malek [this message]
2004-03-31 17:03 ` Matt Porter
2004-03-31 19:57 ` John Whitney
2004-03-31 22:07 ` Matt Porter
2004-03-31 22:25 ` John Whitney
2004-03-31 22:52 ` Dan Malek
2004-04-01 5:30 ` Kumar Gala
2004-03-31 17:01 ` Matt Porter
2004-03-31 17:29 ` Dan Malek
2004-03-31 18:18 ` Christoph Hellwig
2004-03-31 18:40 ` John Whitney
2004-03-31 18:43 ` Christoph Hellwig
2004-03-31 18:50 ` John Whitney
2004-03-31 21:09 ` John Whitney
2004-03-31 21:49 ` Dan Malek
2004-03-31 21:52 ` Eugene Surovegin
2004-03-31 22:07 ` John Whitney
2004-04-01 2:52 ` Benjamin Herrenschmidt
[not found] ` <209F76E4-838B-11D8-9FF0-000A95A07384@sands-edge.com>
[not found] ` <1080790433.1433.59.camel@gaston>
[not found] ` <43B0E668-84BC-11D8-9FF0-000A95A07384@sands-edge.com>
2004-04-03 3:04 ` Benjamin Herrenschmidt
2004-04-03 3:40 ` John Whitney
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=406B0280.1010509@embeddededge.com \
--to=dan@embeddededge.com \
--cc=ebs@ebshome.net \
--cc=johnw@sands-edge.com \
--cc=linuxppc-dev@lists.linuxppc.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).