All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: Jay Cliburn <jacliburn@bellsouth.net>
Cc: csnook@redhat.com, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org, atl1-devel@lists.sourceforge.net
Subject: Re: [PATCH 4/4] atl1: Ancillary C files for Attansic L1 driver
Date: Sat, 27 Jan 2007 17:38:45 -0500	[thread overview]
Message-ID: <45BBD475.4050101@garzik.org> (raw)
In-Reply-To: <45BBCCA2.4090902@bellsouth.net>

Jay Cliburn wrote:
> Jeff Garzik wrote:
>> As a driver maintainer, you need to patch sets, and submit them in a 
>> timely fashion to me.  Note I said patch set, not patch, in following 
>> with Rule #3 from Documentation/SubmittingPatches.  Also make sure to 
>> review http://linux.yyz.us/patch-format.html
> 
> Understood.  Both references reviewed.  Thanks.
> 
> Sorry, but one last question...  These two patches generated overnight 
> by Andrew:
> 
> Message-Id: <200701270710.l0R7AhLj004217@shell0.pdx.osdl.net>
> Subject: + git-netdev-all-atl1-pm-fix.patch added to -mm tree
> 
> and
> 
> Message-Id: <200701270708.l0R78Q0o004191@shell0.pdx.osdl.net>
> Subject: + git-netdev-all-atl1-build-fix.patch added to -mm tree
> 
> Do I include these in my patch set that I submit to you, or do you apply 
> them to netdev directly?

There is no hard and fast rule.  If the patch is obvious and submitted 
in correct form (Andrew's notifications are not in such a form), then I 
might go ahead and apply it.  But I usually reply to the patch with 
"applied" if so.

In general, you can answer this question yourself.  Look at 
netdev-2.6.git#atl1 and see what's in there.

	Jeff




  reply	other threads:[~2007-01-27 22:38 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-21 21:07 [PATCH 4/4] atl1: Ancillary C files for Attansic L1 driver 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 [this message]
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
  -- 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
2006-11-19 20:31 Jay Cliburn
2006-11-20 12:40 ` Chris Snook

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