From: Jeff Garzik <jeff@garzik.org>
To: Richard Knutsson <ricknu-0@student.ltu.se>
Cc: val_henson@linux.intel.com, tulip-users@lists.sourceforge.net,
netdev@vger.kernel.org
Subject: Re: [PATCH] tulip: Convert to generic boolean
Date: Wed, 13 Jun 2007 15:53:27 -0400 [thread overview]
Message-ID: <46704B37.5020509@garzik.org> (raw)
In-Reply-To: <20070519202047.26710.93680.sendpatchset@thinktank.campus.ltu.se>
Richard Knutsson wrote:
> Signed-off-by: Richard Knutsson <ricknu-0@student.ltu.se>
> ---
> Compile-tested with all(yes|mod|no)config on x86(|_64) & sparc(|64)
> Diffed against Linus' git-tree.
>
> de4x5.c | 98 ++++++++++++++++++++++++++++++++--------------------------------
> de4x5.h | 9 -----
> 2 files changed, 49 insertions(+), 58 deletions(-)
applied to #upstream
prev parent reply other threads:[~2007-06-13 19:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-19 20:18 [PATCH] tulip: Convert to generic boolean Richard Knutsson
2007-06-13 19:53 ` 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=46704B37.5020509@garzik.org \
--to=jeff@garzik.org \
--cc=netdev@vger.kernel.org \
--cc=ricknu-0@student.ltu.se \
--cc=tulip-users@lists.sourceforge.net \
--cc=val_henson@linux.intel.com \
/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).