From: chetan loke <loke.chetan@gmail.com>
To: davem@davemloft.net, netdev@vger.kernel.org
Cc: eric.dumazet@gmail.com, joe@perches.com,
bhutchings@solarflare.com, shemminger@vyatta.com,
linux-kernel@vger.kernel.org, Chetan Loke <loke.chetan@gmail.com>
Subject: Re: [PATCH v2 net-next af-packet 0/2] Enhance af-packet to provide (near zero)lossless packet capture functionality.
Date: Tue, 21 Jun 2011 23:02:11 -0400 [thread overview]
Message-ID: <BANLkTimisxLVdYJTK1NcR1vQi27CE20yxQ@mail.gmail.com> (raw)
In-Reply-To: <1308708650-25509-1-git-send-email-loke.chetan@gmail.com>
On Tue, Jun 21, 2011 at 10:10 PM, Chetan Loke <loke.chetan@gmail.com> wrote:
> Hello,
>
> Please review the patchset.
>
> Changes from v1:
>
> 1) v1 was based on 2.6.38.9. v2 is rebased to net-next.
> 2) Aligned bdqc members, pr_err to WARN, sob email (Joe Perches)
> 3) Added tp_padding (Eric Dumazet)
> 4) Nuked useless ;) white space (Stephen H)
> 5) Use __u types in headers (Ben Hutchings)
> 6) Added field for creating private area (Chetan Loke)
>
Hi Dave,
Is there a chance of getting this merged either in 3.0 or 3.1 or ever ;) ?
thanks
Chetan
next prev parent reply other threads:[~2011-06-22 3:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-22 2:10 [PATCH v2 net-next af-packet 0/2] Enhance af-packet to provide (near zero)lossless packet capture functionality Chetan Loke
2011-06-22 2:10 ` [PATCH v2 net-next af-packet 1/2] " Chetan Loke
2011-07-01 22:36 ` David Miller
2011-07-05 14:53 ` chetan loke
2011-07-05 15:01 ` David Miller
2011-07-06 21:45 ` chetan loke
2011-07-07 7:13 ` David Miller
2011-07-07 13:04 ` chetan loke
2011-07-07 13:11 ` David Miller
2011-06-22 2:10 ` [PATCH v2 net-next af-packet 2/2] " Chetan Loke
2011-06-22 3:02 ` chetan loke [this message]
2011-06-22 8:35 ` [PATCH v2 net-next af-packet 0/2] " 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=BANLkTimisxLVdYJTK1NcR1vQi27CE20yxQ@mail.gmail.com \
--to=loke.chetan@gmail.com \
--cc=bhutchings@solarflare.com \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=shemminger@vyatta.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).