netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@redhat.com>
To: kazunori@miyazawa.org
Cc: kuznet@ms2.inr.ac.ru, usagi@linux-ipv6.org, netdev@oss.sgi.com
Subject: Re: [PATCH][IPV6] fix ipv6 header handling of AH input.
Date: Sun, 15 Jun 2003 06:15:00 -0700 (PDT)	[thread overview]
Message-ID: <20030615.061500.78718230.davem@redhat.com> (raw)
In-Reply-To: <20030615220632.0701a5cd.kazunori@miyazawa.org>

   From: Kazunori Miyazawa <kazunori@miyazawa.org>
   Date: Sun, 15 Jun 2003 22:06:32 +0900

   This patch fixes ipv6 header handling of ah input and moves
   the routine to clear mutable options.
   It reduces unnecessary header clearing when a packet has only ESP.
   
   This patch for linux-2.5.70 + CS1.1307

Thank you very much, I have applied your patch.

      reply	other threads:[~2003-06-15 13:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-15 13:06 [PATCH][IPV6] fix ipv6 header handling of AH input Kazunori Miyazawa
2003-06-15 13:15 ` 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=20030615.061500.78718230.davem@redhat.com \
    --to=davem@redhat.com \
    --cc=kazunori@miyazawa.org \
    --cc=kuznet@ms2.inr.ac.ru \
    --cc=netdev@oss.sgi.com \
    --cc=usagi@linux-ipv6.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).