From: David Miller <davem@davemloft.net>
To: scott.a.mcmillan@intel.com
Cc: netdev@vger.kernel.org, tcpdump-workers@lists.tcpdump.org
Subject: Re: [PATCH] packet_mmap: expose hw packet timestamps to network packet capture utilities
Date: Sat, 29 May 2010 00:11:08 -0700 (PDT) [thread overview]
Message-ID: <20100529.001108.91328843.davem@davemloft.net> (raw)
In-Reply-To: <09ED21B37E0F694688A2317C4FED9ED3046E53F595@azsmsx504.amr.corp.intel.com>
From: "Mcmillan, Scott A" <scott.a.mcmillan@intel.com>
Date: Thu, 27 May 2010 09:58:19 -0700
> There was no negative feedback on this RFC, and the corresponding
> tcpdump patch was well received. Please apply.
I think lack of feedback is not an indication of agreement.
You sent that patch right around the openning of the merge window when
people (myself included) are already overwhelmed with existing tasks.
New patches aren't likely to get serious consideration during that
time.
next prev parent reply other threads:[~2010-05-29 7:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-21 20:24 [RFC PATCH] packet_mmap: expose hw packet timestamps to network packet capture utilities Mcmillan, Scott A
2010-05-27 16:58 ` [PATCH] " Mcmillan, Scott A
2010-05-29 7:11 ` David Miller [this message]
2010-06-02 12:54 ` David Miller
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=20100529.001108.91328843.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=scott.a.mcmillan@intel.com \
--cc=tcpdump-workers@lists.tcpdump.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).