netdev - Re: [PATCH 1/2] net: at91_ether.c - Allow transmitter interrupt to be handled first in ISR

lists.openwall.net		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 linux-cve-announce 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:	Fri, 15 Jan 2010 06:38:25 +0100
From:	Eric Dumazet <eric.dumazet@...il.com>
To:	James Kosin <JKosin@...comgrp.com>
CC:	David Miller <davem@...emloft.net>, linux-kernel@...r.kernel.org,
	netdev@...r.kernel.org
Subject: Re: [PATCH 1/2] net: at91_ether.c - Allow transmitter interrupt to
 be handled first in ISR

Le 14/01/2010 21:28, James Kosin a écrit :
> Thanks David,
> 
> I'm checking out the latest git://git.kernel.org/pub/scm/linux/kernel/git/davem/net-2.6.git
> With git now...
> 
> A few items:
> 	a)  Is it OK to use git-diff to build a patch file?  Or does everyone still prefer
> 	    diff?

If you cook your patches using a git tree, git diff is very fine to send official patches.

> 
> 	b)  I'm going to try and test also; since, I do have an active platform I
> 	    can test on.  Are there any other developers using the ARM that may be able
> 	    to provide some feedback?  Eric Dumazet had some interesting comments
> 	    but, none of the original people in the file are around anymore I'm afraid.
> 	    That or they really don't want to be contacted.

If you can test patches, and other dev can review them, they can find their way in kernel,
dont worry :)
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html