All of lore.kernel.org
 help / color / mirror / Atom feed
From: Neil Horman <nhorman@tuxdriver.com>
To: David Miller <davem@davemloft.net>
Cc: dada1@cosmosbay.com, jpirko@redhat.com,
	paulmck@linux.vnet.ibm.com, netdev@vger.kernel.org
Subject: Re: [PATCH] dropmon: add ability to detect when hardware dropsrxpackets
Date: Thu, 21 May 2009 20:09:00 -0400	[thread overview]
Message-ID: <20090522000900.GA2715@localhost.localdomain> (raw)
In-Reply-To: <20090521.151503.231694262.davem@davemloft.net>

On Thu, May 21, 2009 at 03:15:03PM -0700, David Miller wrote:
> From: Neil Horman <nhorman@tuxdriver.com>
> Date: Thu, 21 May 2009 13:36:08 -0400
> 
> > Thank you Dave, copy n' paste bit me.
> > 
> > Patch v6
> 
> Applied to net-next-2.6, thanks!
> 


Thanks Dave.  I'll try get it right the first try next time around.


Ok, maybe the third try :)
Neil


  reply	other threads:[~2009-05-22  0:09 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-08 19:50 [PATCH] dropmon: add ability to detect when hardware drops rx packets Neil Horman
2009-05-09  6:30 ` Eric Dumazet
2009-05-09 18:07   ` Neil Horman
2009-05-12 16:30   ` Neil Horman
2009-05-13 18:23     ` [PATCH] dropmon: add ability to detect when hardware drops rxpackets Paul E. McKenney
2009-05-14  0:45       ` Neil Horman
2009-05-14  1:03         ` [PATCH] dropmon: add ability to detect when hardware dropsrxpackets Paul E. McKenney
2009-05-14 12:33           ` Neil Horman
2009-05-14 12:44             ` Jiri Pirko
2009-05-14 16:17               ` [PATCH] dropmon: add ability to detect when hardwaredropsrxpackets Paul E. McKenney
2009-05-14 17:29               ` [PATCH] dropmon: add ability to detect when hardware dropsrxpackets Neil Horman
2009-05-15  5:49                 ` Jarek Poplawski
2009-05-15 11:01                   ` Neil Horman
2009-05-15 11:12                     ` Jarek Poplawski
2009-05-15 11:15                       ` Neil Horman
2009-05-15 11:40                         ` Jarek Poplawski
2009-05-16  0:07                           ` Paul E. McKenney
2009-05-15  6:51                 ` Jiri Pirko
2009-05-15  7:37                   ` Eric Dumazet
2009-05-15 11:12                     ` Neil Horman
2009-05-15 10:59                   ` Neil Horman
2009-05-15 11:27                     ` Jiri Pirko
2009-05-15 16:07                       ` Neil Horman
2009-05-15 18:11                         ` Eric Dumazet
2009-05-15 18:23                           ` Stephen Hemminger
2009-05-15 19:53                             ` Neil Horman
2009-05-15 19:23                           ` Neil Horman
2009-05-16 12:40                           ` Neil Horman
2009-05-18 14:46                             ` Neil Horman
2009-05-21  7:17                               ` David Miller
2009-05-21 17:36                                 ` Neil Horman
2009-05-21 22:15                                   ` David Miller
2009-05-22  0:09                                     ` Neil Horman [this message]
2009-05-15 18:18                         ` Stephen Hemminger
2009-05-15 19:12                           ` Neil Horman
2009-05-14 16:18             ` [PATCH] dropmon: add ability to detect when hardwaredropsrxpackets Paul E. McKenney

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=20090522000900.GA2715@localhost.localdomain \
    --to=nhorman@tuxdriver.com \
    --cc=dada1@cosmosbay.com \
    --cc=davem@davemloft.net \
    --cc=jpirko@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=paulmck@linux.vnet.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.