From: Shmulik Hen <shmulik.hen@intel.com>
To: "Stephen Hemminger" <shemminger@osdl.org>
Cc: "James Morris" <jmorris@intercode.com.au>,
<bonding-devel@lists.sourceforge.net>, <netdev@oss.sgi.com>
Subject: Re: [PATCH] convering bonding driver /proc interface to seq_file
Date: Tue, 26 Aug 2003 10:45:16 +0300 [thread overview]
Message-ID: <200308261045.16910.shmulik.hen@intel.com> (raw)
In-Reply-To: <E791C176A6139242A988ABA8B3D9B38A0251EB62@hasmsx403.iil.intel.com>
On Monday 25 August 2003 10:27 pm, Stephen Hemminger wrote:
>
> #ifndef PDE
> #define PDE(i) ((struct proc_dir_entry *)(i)->u.generic_ip)
> #endif
When you're right, you're right. We didn't know we could do that
safely in 2.4.
How about the following suggestion:
I'll take it as my personal commitment to implement the fix you've
suggested, along with that of James, but only after the 2.4<->2.6
synchronization is complete.
After all, my word is my bond(ing) :)
--
| Shmulik Hen Advanced Network Services |
| Israel Design Center, Jerusalem |
| LAN Access Division, Platform Networking |
| Intel Communications Group, Intel corp. |
next parent reply other threads:[~2003-08-26 7:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E791C176A6139242A988ABA8B3D9B38A0251EB62@hasmsx403.iil.intel.com>
2003-08-26 7:45 ` Shmulik Hen [this message]
2003-08-25 18:43 [PATCH] convering bonding driver /proc interface to seq_file Hen, Shmulik
2003-08-25 19:27 ` Stephen Hemminger
-- strict thread matches above, loose matches on Subject: below --
2003-08-23 14:25 Hen, Shmulik
2003-08-24 15:15 ` James Morris
2003-08-24 17:12 ` Shmulik Hen
2003-08-25 15:45 ` Stephen Hemminger
2003-08-23 13:35 Hen, Shmulik
2003-08-21 23:52 Stephen Hemminger
2003-08-22 0:17 ` James Morris
2003-08-22 0:27 ` Chad N. Tindel
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=200308261045.16910.shmulik.hen@intel.com \
--to=shmulik.hen@intel.com \
--cc=bonding-devel@lists.sourceforge.net \
--cc=jmorris@intercode.com.au \
--cc=netdev@oss.sgi.com \
--cc=shemminger@osdl.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).