From: "David S. Miller" <davem@redhat.com>
To: Steve@ChyGwyn.com, steve@gw.chygwyn.com
Cc: linux-decnet-user@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: Remains of seq_file conversion for DECnet, plus fixes
Date: Thu, 01 May 2003 05:45:23 -0700 (PDT) [thread overview]
Message-ID: <20030501.054523.98892534.davem@redhat.com> (raw)
In-Reply-To: <200305011327.OAA16943@gw.chygwyn.com>
From: Steven Whitehouse <steve@gw.chygwyn.com>
Date: Thu, 1 May 2003 14:27:08 +0100 (BST)
Its got big again, so I've put it here, if you'd like it in bits rather than
all one lump, just shout:
Please do this because it's easier for me to evaluate small patches
doing one thing at a time and you're also making modifications to
things outside of decnet.
About update_pmtu(). You are not required to implement this.
All of these places you see dereferencing dst->update_mtu()
know that they have an ipv4/ipv6 route. Or do you know some
exception to this?
next prev parent reply other threads:[~2003-05-01 13:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20030421.234303.59654654.davem@redhat.com>
2003-05-01 13:27 ` Remains of seq_file conversion for DECnet, plus fixes Steven Whitehouse
2003-05-01 12:45 ` David S. Miller [this message]
2003-05-01 14:04 ` Steven Whitehouse
2003-05-01 13:09 ` David S. Miller
2003-05-01 20:52 ` Steven Whitehouse
2003-05-01 20:57 ` Christoph Hellwig
2003-05-01 21:35 ` Steven Whitehouse
2003-05-01 21:22 ` David S. Miller
2003-05-02 1:54 ` Arnaldo Carvalho de Melo
2003-05-04 18:43 ` Steven Whitehouse
2003-05-06 6:46 ` David S. Miller
2003-05-01 20:55 ` Remains of seq_file conversion for DECnet, plus fixes (part 2) Steven Whitehouse
2003-05-01 20:57 ` Remains of seq_file conversion for DECnet, plus fixes (part 3) Steven Whitehouse
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=20030501.054523.98892534.davem@redhat.com \
--to=davem@redhat.com \
--cc=Steve@ChyGwyn.com \
--cc=linux-decnet-user@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=steve@gw.chygwyn.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).