netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: Jay Cliburn <jacliburn@bellsouth.net>
Cc: shemminger@osdl.org, csnook@redhat.com, hch@infradead.org,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	atl1-devel@lists.sourceforge.net
Subject: Re: [PATCH 0/4] atl1: Attansic L1 ethernet driver
Date: Tue, 23 Jan 2007 16:27:25 -0500	[thread overview]
Message-ID: <45B67DBD.2060300@garzik.org> (raw)
In-Reply-To: <45B63ADC.8060808@bellsouth.net>

Jay Cliburn wrote:
> Perhaps a dumb question, but when can I begin submitting differential 
> patches?  Now?  I'd like to incorporate some of Arjan's and Randy's 
> comments.

Submit patches starting... now!  :)

	Jeff

  reply	other threads:[~2007-01-23 21:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-21 21:04 [PATCH 0/4] atl1: Attansic L1 ethernet driver Jay Cliburn
2007-01-23  5:57 ` Jeff Garzik
2007-01-23 16:42   ` Jay Cliburn
2007-01-23 21:27     ` Jeff Garzik [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-01-11  0:39 Jay Cliburn

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=45B67DBD.2060300@garzik.org \
    --to=jeff@garzik.org \
    --cc=atl1-devel@lists.sourceforge.net \
    --cc=csnook@redhat.com \
    --cc=hch@infradead.org \
    --cc=jacliburn@bellsouth.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --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 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).