From: linas@austin.ibm.com (Linas Vepstas)
To: Ishizaki Kou <kou.ishizaki@toshiba.co.jp>
Cc: netdev@vger.kernel.org, cbe-oss-dev@ozlabs.org
Subject: Re: [PATCH] spidernet: improve interrupt handling
Date: Mon, 9 Jul 2007 17:19:22 -0500 [thread overview]
Message-ID: <20070709221922.GP4457@austin.ibm.com> (raw)
In-Reply-To: <20070709.174808.-1350520249.kouish@swc.toshiba.co.jp>
On Mon, Jul 09, 2007 at 05:48:08PM +0900, Ishizaki Kou wrote:
> We intend this patch to improve spidernet interrupt handling to be
> more strict. We had following problem and this patch solves it.
Looks reasonable to me. I'll forward it upstream. In the future,
could you use "diff -Nupr"? it adds some extra information
(the name of the subroutine) to the patch chunks; this makes
it easier to read.
QUILT_DIFF_OPTS="-Nupr"
in ~/.quiltrc if you use quilt.
--linas
next prev parent reply other threads:[~2007-07-09 22:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-09 8:48 [PATCH] spidernet: improve interrupt handling Ishizaki Kou
2007-07-09 22:19 ` Linas Vepstas [this message]
2007-07-11 4:57 ` [Cbe-oss-dev] " Ishizaki Kou
-- strict thread matches above, loose matches on Subject: below --
2007-07-09 23:17 Linas Vepstas
2007-07-10 16:25 ` Jeff Garzik
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=20070709221922.GP4457@austin.ibm.com \
--to=linas@austin.ibm.com \
--cc=cbe-oss-dev@ozlabs.org \
--cc=kou.ishizaki@toshiba.co.jp \
--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.