From: Jeff Garzik <jgarzik@pobox.com>
To: Ayaz Abdulla <aabdulla@nvidia.com>
Cc: Manfred Spraul <manfred@colorfullife.com>,
Andrew Morton <akpm@osdl.org>,
netdev@vger.kernel.org
Subject: Re: [PATCH 2/12] forcedeth: ring access
Date: Thu, 18 Jan 2007 21:51:14 -0500 [thread overview]
Message-ID: <45B03222.9030802@pobox.com> (raw)
In-Reply-To: <45A3DF2F.10202@nvidia.com>
Ayaz Abdulla wrote:
> This patch modifys ring access by using pointers. This avoids computing
> the current index and avoids accessing the base address of the rings.
>
> Signed-Off-By: Ayaz Abdulla <aabdulla@nvidia.com>
ACK patches 1-9.
Applied patches 1-4 successfully, patch #5 failed to apply. Please
resend patches 5+ against netdev-2.6.git#upstream.
Also, git-am (the git component used to apply yours and others' patches)
complains that your patches have spaces prior to the tab indentations.
Fixing that in patches 5+, or appending a final whitespace cleanup
patch, would be appreciated.
Jeff
prev parent reply other threads:[~2007-01-19 2:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-09 18:30 [PATCH 2/12] forcedeth: ring access Ayaz Abdulla
2007-01-19 2:51 ` Jeff Garzik [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=45B03222.9030802@pobox.com \
--to=jgarzik@pobox.com \
--cc=aabdulla@nvidia.com \
--cc=akpm@osdl.org \
--cc=manfred@colorfullife.com \
--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).