From: Jeff Garzik <jeff@garzik.org>
To: Brice Goglin <brice@myri.com>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH 3/2] myri10ge: fix copyright and license
Date: Tue, 27 Feb 2007 04:15:22 -0500 [thread overview]
Message-ID: <45E3F6AA.5000202@garzik.org> (raw)
In-Reply-To: <45DF4C99.90104@myri.com>
Brice Goglin wrote:
> Fix copyright and license ("regents" should not have ever been used).
>
> Signed-off-by: Brice Goglin <brice@myri.com>
> ---
> drivers/net/myri10ge/myri10ge.c | 22 +++++++++++-----------
> 1 file changed, 11 insertions(+), 11 deletions(-)
ACK, but dropped since patch #2 was dropped
next prev parent reply other threads:[~2007-02-27 9:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-21 17:04 [PATCH 0/2] myri10ge updates Brice Goglin
2007-02-21 17:05 ` [PATCH 1/2] myri10ge: workaround buggy adopted firmwares Brice Goglin
2007-02-27 9:16 ` Jeff Garzik
2007-02-21 17:06 ` [PATCH 2/2] myri10ge: large receive offload Brice Goglin
2007-02-27 9:15 ` Jeff Garzik
2007-02-23 20:20 ` [PATCH 3/2] myri10ge: fix copyright and license Brice Goglin
2007-02-27 9:15 ` Jeff Garzik [this message]
2007-02-23 20:22 ` [PATCH 0/2] myri10ge updates Brice Goglin
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=45E3F6AA.5000202@garzik.org \
--to=jeff@garzik.org \
--cc=brice@myri.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).