All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Snook <csnook@redhat.com>
To: Jay Cliburn <jacliburn@bellsouth.net>
Cc: jeff@garzik.org, shemminger@osdl.org, romieu@fr.zoreil.com,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 4/4] atl1: Ancillary C files for Attansic L1 driver
Date: Mon, 20 Nov 2006 07:40:46 -0500	[thread overview]
Message-ID: <4561A24E.2030405@redhat.com> (raw)
In-Reply-To: <20061119203137.GE29736@osprey.hogchain.net>

Jay Cliburn wrote:
> From: Jay Cliburn <jacliburn@bellsouth.net>
> 
> This patch contains auxiliary C files for the Attansic L1 gigabit ethernet
> adapter driver.
> 
> Signed-off-by: Jay Cliburn <jacliburn@bellsouth.net>
> ---
I've been working with Jay on a lot of the cleanup of this driver since 
his original submission.

Signed-off-by: Chris Snook <csnook@redhat.com>

  reply	other threads:[~2006-11-20 12:47 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-19 20:31 [PATCH 4/4] atl1: Ancillary C files for Attansic L1 driver Jay Cliburn
2006-11-20 12:40 ` Chris Snook [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-01-11  0:43 Jay Cliburn
2007-01-11  9:37 ` Christoph Hellwig
2007-01-19  3:00 ` Jeff Garzik
2007-01-21 21:07 Jay Cliburn
2007-01-22  2:31 ` Randy Dunlap
2007-01-22  3:33   ` Jay Cliburn
2007-01-22 20:00     ` Luca Tettamanti
2007-01-23 19:25       ` Stephen Hemminger
2007-01-23 21:19         ` Luca Tettamanti
2007-01-27 21:02           ` Jay Cliburn
2007-01-27 21:15             ` Jeff Garzik
2007-01-27 22:05               ` Jay Cliburn
2007-01-27 22:38                 ` Jeff Garzik
2007-01-23 21:33         ` Jeff Garzik
2007-01-23 21:34           ` Stephen Hemminger
2007-01-23 21:46             ` Randy Dunlap
2007-01-23 22:06               ` Jeff Garzik

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=4561A24E.2030405@redhat.com \
    --to=csnook@redhat.com \
    --cc=jacliburn@bellsouth.net \
    --cc=jeff@garzik.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=romieu@fr.zoreil.com \
    --cc=shemminger@osdl.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 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.