From: Pavel Roskin <proski@gnu.org>
To: Dave <kilroyd@googlemail.com>
Cc: Andrey Borzenkov <arvidjaar@mail.ru>,
orinoco-devel@lists.sourceforge.net,
linux-wireless@vger.kernel.org
Subject: Re: [Orinoco-devel] [PATCH] orinoco: trivial cleanup in alloc_orinocodev
Date: Wed, 21 Jan 2009 15:46:20 -0500 [thread overview]
Message-ID: <1232570780.10843.14.camel@dv> (raw)
In-Reply-To: <49778657.8020902@gmail.com>
On Wed, 2009-01-21 at 20:32 +0000, Dave wrote:
> I've a patch series reorganising the orinoco driver a bit to help with
> future changes. It should fix a good proportion of those warnings. I
> plan to post it soon - so I'd appreciate it if you held off submitting
> further cleanup patches until I get it done (I'll try for the end of
> this week).
>
> I should be able to rebase around this one.
OK, good to know.
--
Regards,
Pavel Roskin
next prev parent reply other threads:[~2009-01-21 20:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-21 18:55 [PATCH] orinoco: trivial cleanup in alloc_orinocodev Andrey Borzenkov
2009-01-21 20:21 ` [Orinoco-devel] " Pavel Roskin
2009-01-21 20:32 ` Dave
2009-01-21 20:46 ` Pavel Roskin [this message]
2009-01-22 9:19 ` Kalle Valo
2009-01-22 16:33 ` Pavel Roskin
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=1232570780.10843.14.camel@dv \
--to=proski@gnu.org \
--cc=arvidjaar@mail.ru \
--cc=kilroyd@googlemail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=orinoco-devel@lists.sourceforge.net \
/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).