lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:	Sat, 27 Jan 2007 17:38:45 -0500
From:	Jeff Garzik <>
To:	Jay Cliburn <>
Subject: Re: [PATCH 4/4] atl1: Ancillary C files for Attansic L1 driver

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
> Understood.  Both references reviewed.  Thanks.
> Sorry, but one last question...  These two patches generated overnight 
> by Andrew:
> Message-Id: <>
> Subject: + git-netdev-all-atl1-pm-fix.patch added to -mm tree
> and
> Message-Id: <>
> 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.


To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to
More majordomo info at

Powered by blists - more mailing lists