From: "John W. Linville" <linville@tuxdriver.com>
To: Pavel Roskin <proski@gnu.org>
Cc: Dan Williams <dcbw@redhat.com>, netdev@vger.kernel.org
Subject: Re: orinoco encodeext + auth patch on lkml
Date: Mon, 5 Jun 2006 15:02:23 -0400 [thread overview]
Message-ID: <20060605190218.GI6068@tuxdriver.com> (raw)
In-Reply-To: <1149226685.7053.10.camel@dv>
On Fri, Jun 02, 2006 at 01:38:05AM -0400, Pavel Roskin wrote:
> Hello, Dan!
>
> On Wed, 2006-05-31 at 08:03 -0400, Dan Williams wrote:
> > Pavel,
> >
> > Unsure if you saw this. Slightly annoying he didn't send to netdev, but
> > would be good to take a look at and possibly integrate. Looks sane to
> > me from 10,000ft.
> >
> > http://lkml.org/lkml/2006/5/30/433
>
> Thanks for heads up. Actually, this e-mail was copied to the orinoco
> mailing list, so I'm aware of it.
Pavel,
I'll count on you to pass this along if/when you feel it is appropriate.
John
--
John W. Linville
linville@tuxdriver.com
prev parent reply other threads:[~2006-06-05 19:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-31 12:03 orinoco encodeext + auth patch on lkml Dan Williams
2006-06-02 5:38 ` Pavel Roskin
2006-06-05 19:02 ` John W. Linville [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=20060605190218.GI6068@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=dcbw@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=proski@gnu.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).