netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "J. K. Cliburn" <jcliburn@gmail.com>
To: jeff@garzik.org
Cc: jcliburn@gmail.com, csnook@redhat.com, jie.yang@atheros.com,
	ramon.casellas@cttc.es, netdev@vger.kernel.org,
	stable@kernel.org
Subject: Re: [PATCH] atl1: fix vlan tag regression
Date: Wed, 29 Oct 2008 10:45:45 -0500	[thread overview]
Message-ID: <49088529.8060602@gmail.com> (raw)
In-Reply-To: <20081029154050.GA13726@osprey.hogchain.net>

Jay Cliburn wrote:
> Commit 401c0aabec4b97320f962a0161a846d230a6f7aa introduced a regression
> in the atl1 driver by storing the VLAN tag in the wrong TX descriptor
> field.
> 
> This patch causes the VLAN tag to be stored in its proper location.

Argh.  The patch is whitespace damaged.  Will resubmit shortly.

      reply	other threads:[~2008-10-29 15:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-29 15:40 [PATCH] atl1: fix vlan tag regression Jay Cliburn
2008-10-29 15:45 ` J. K. Cliburn [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=49088529.8060602@gmail.com \
    --to=jcliburn@gmail.com \
    --cc=csnook@redhat.com \
    --cc=jeff@garzik.org \
    --cc=jie.yang@atheros.com \
    --cc=netdev@vger.kernel.org \
    --cc=ramon.casellas@cttc.es \
    --cc=stable@kernel.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).