From: Eric Dumazet <eric.dumazet@gmail.com>
To: James Kosin <JKosin@intcomgrp.com>
Cc: David Miller <davem@davemloft.net>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH 1/2] net: at91_ether.c - Allow transmitter interrupt to be handled first in ISR
Date: Fri, 15 Jan 2010 06:38:25 +0100 [thread overview]
Message-ID: <4B4FFF51.6020803@gmail.com> (raw)
In-Reply-To: <3DBBD805E3BA064A87F551C0E8BD367402897539@MAILSRV.intcomgrp.com>
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 :)
prev parent reply other threads:[~2010-01-15 5:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-13 17:25 [PATCH 1/2] net: at91_ether.c - Allow transmitter interrupt to be handled first in ISR James Kosin
2010-01-14 1:32 ` David Miller
2010-01-14 1:40 ` netdev: patchwork.ozlabs.org vs patchwork.kernel.org ? Joe Perches
2010-01-14 1:41 ` David Miller
2010-01-14 1:49 ` Joe Perches
2010-01-14 20:28 ` [PATCH 1/2] net: at91_ether.c - Allow transmitter interrupt to be handled first in ISR James Kosin
2010-01-15 5:38 ` Eric Dumazet [this message]
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=4B4FFF51.6020803@gmail.com \
--to=eric.dumazet@gmail.com \
--cc=JKosin@intcomgrp.com \
--cc=davem@davemloft.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 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).