From: Jeff Garzik <jgarzik@pobox.com>
To: mcgrof@ruslug.rutgers.edu
Cc: Andrew Morton <akpm@osdl.org>, Netdev <netdev@oss.sgi.com>,
Marcelo Tosatti <marcelo@conectiva.com.br>,
prism54-devel@prism54.org,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2.4.26] prism54: add prism54 1.2
Date: Wed, 23 Jun 2004 07:48:32 -0400 [thread overview]
Message-ID: <40D96E10.1060203@pobox.com> (raw)
In-Reply-To: <20040623054348.GV6253@ruslug.rutgers.edu>
mcgrof@ruslug.rutgers.edu wrote:
> Andrew,
>
> 2.6.7-bk5 and 2.6.7-mm1 are both in perfect sync with prism54
> cvs tree now. This completes our 1.2 release. As promised,
> the attached patch adds prism54 1.2 to 2.4 kernel tree.
Andrew is a 2.6-only guy.
This is totally up to Marcelo whether to merge this new wireless stuff
or not...
Jeff
next prev parent reply other threads:[~2004-06-23 11:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-23 5:43 [PATCH 2.4.26] prism54: add prism54 1.2 mcgrof
2004-06-23 11:48 ` Jeff Garzik [this message]
2004-06-23 16:41 ` Luis R. Rodriguez
2004-06-24 18:34 ` Marcelo Tosatti
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=40D96E10.1060203@pobox.com \
--to=jgarzik@pobox.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
--cc=mcgrof@ruslug.rutgers.edu \
--cc=netdev@oss.sgi.com \
--cc=prism54-devel@prism54.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).