From: "David S. Miller" <davem@redhat.com>
To: Shirley Ma <mashirle@us.ibm.com>
Cc: kuznet@ms2.inr.ac.ru, netdev@oss.sgi.com
Subject: Re: [PATCH] New Patch Implementation for IPv6 MIB:ipv6InterfaceTable
Date: Thu, 15 Jan 2004 00:55:03 -0800 [thread overview]
Message-ID: <20040115005503.63f4cbc7.davem@redhat.com> (raw)
In-Reply-To: <200401141448.55531.mashirle@us.ibm.com>
On Wed, 14 Jan 2004 14:48:55 -0800
Shirley Ma <mashirle@us.ibm.com> wrote:
> > It looks fine but I cannot merge it at this time. Linus wants
> > only critical bug fixes for nowin 2.6.x
> >
> > Maybe in 2.6.1, 2.6.2 or later we can merge this in.
>
> This patch is against 2.6.1 kernel.
Applied, thanks.
prev parent reply other threads:[~2004-01-15 8:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-14 17:32 [PATCH]Implementation for IPv6 MIB:ipv6InterfaceTable Shirley Ma
2003-10-14 22:24 ` David S. Miller
2003-10-20 23:00 ` [PATCH] New Patch Implementation " Shirley Ma
2003-10-20 23:43 ` Shirley Ma
2003-10-21 4:04 ` David S. Miller
2004-01-14 22:48 ` Shirley Ma
2004-01-15 8:55 ` 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=20040115005503.63f4cbc7.davem@redhat.com \
--to=davem@redhat.com \
--cc=kuznet@ms2.inr.ac.ru \
--cc=mashirle@us.ibm.com \
--cc=netdev@oss.sgi.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).