netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@redhat.com>
To: Steve@ChyGwyn.com, steve@gw.chygwyn.com
Cc: netdev@oss.sgi.com
Subject: Re: ip_gre.c:ipgre_tunnel_xmit() duplicated code ?
Date: Mon, 21 Apr 2003 23:43:03 -0700 (PDT)	[thread overview]
Message-ID: <20030421.234303.59654654.davem@redhat.com> (raw)
In-Reply-To: <200304211021.LAA21942@gw.chygwyn.com>

   From: Steven Whitehouse <steve@gw.chygwyn.com>
   Date: Mon, 21 Apr 2003 11:21:59 +0100 (BST)

   I found some code in ip_gre.c which looks to be duplicated. Is the
   attached the right fix or did I miss something? 

You're right, I've integrated your fix thanks.

      reply	other threads:[~2003-04-22  6:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20030418.034241.38698733.davem@redhat.com>
2003-04-21 10:21 ` ip_gre.c:ipgre_tunnel_xmit() duplicated code ? Steven Whitehouse
2003-04-22  6:43   ` David S. Miller [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=20030421.234303.59654654.davem@redhat.com \
    --to=davem@redhat.com \
    --cc=Steve@ChyGwyn.com \
    --cc=netdev@oss.sgi.com \
    --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).