netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: ajones@riverbed.com
Cc: jeffrey.t.kirsher@intel.com, netdev@vger.kernel.org,
	gospo@redhat.com, Arthur.Jones@riverbed.com,
	shemminger@vyatta.com, alexander.h.duyck@intel.com
Subject: Re: [next-next PATCH] e1000e: fixup merge error
Date: Fri, 20 Mar 2009 15:56:44 -0700 (PDT)	[thread overview]
Message-ID: <20090320.155644.86516049.davem@davemloft.net> (raw)
In-Reply-To: <20090320152447.GA28023@ajones-laptop.nbttech.com>

From: Arthur Jones <ajones@riverbed.com>
Date: Fri, 20 Mar 2009 08:24:47 -0700

> When merging into Jeff's tree:
> 
> 	commit 5f66f208064f083aab5e55935d0575892e033b59
> 	Author: Arthur Jones <ajones@riverbed.com>
> 	Date:   Thu Mar 19 01:13:08 2009 +0000
> 
> 	    e1000e: allow tx of pre-formatted vlan tagged packets
> 
> We lost one line, this fixes that missing
> piece...
> 
> Signed-off-by: Arthur Jones <ajones@riverbed.com>

Applied, thanks Arthur.

  reply	other threads:[~2009-03-20 22:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-19 11:12 [net-next PATCH 1/3] e1000e: add support for 82583 device id Jeff Kirsher
2009-03-19 11:12 ` [net-next PATCH 2/3] e1000e: fix dma error handling issues Jeff Kirsher
2009-03-20  8:31   ` David Miller
2009-03-19 11:13 ` [net-next PATCH 3/3] e1000e: allow tx of pre-formatted vlan tagged packets Jeff Kirsher
2009-03-20  8:31   ` David Miller
2009-03-20 15:24     ` [next-next PATCH] e1000e: fixup merge error Arthur Jones
2009-03-20 22:56       ` David Miller [this message]
2009-03-20  8:31 ` [net-next PATCH 1/3] e1000e: add support for 82583 device id 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=20090320.155644.86516049.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=Arthur.Jones@riverbed.com \
    --cc=ajones@riverbed.com \
    --cc=alexander.h.duyck@intel.com \
    --cc=gospo@redhat.com \
    --cc=jeffrey.t.kirsher@intel.com \
    --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).