From: Johannes Berg <johannes@sipsolutions.net>
To: Dave <kilroyd@googlemail.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [RFC] wireless: Add channel/frequency conversions
Date: Mon, 22 Dec 2008 11:49:08 +0100 [thread overview]
Message-ID: <c78e595374b4ebeef303c2bf12982735@localhost> (raw)
In-Reply-To: <494F6BE6.60009@gmail.com> (sfid-20081222_112903_735110_0C849BF0)
On Mon, 22 Dec 2008 10:28:54 +0000, Dave <kilroyd@googlemail.com> wrote:
> I didn't quite get what you meant by that last statement - did you mean
> that the inlining is OK, or that you'd prefer them not inlined?
>
> If you meant the former (and there aren't any strong opinions about
> lib80211), I'll just submit as is.
Sorry, I meant it's fine, go ahead.
johannes
prev parent reply other threads:[~2008-12-22 10:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-20 18:31 [RFC] wireless: Add channel/frequency conversions David Kilroy
2008-12-21 10:36 ` Johannes Berg
2008-12-22 10:28 ` Dave
2008-12-22 10:49 ` Johannes Berg [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=c78e595374b4ebeef303c2bf12982735@localhost \
--to=johannes@sipsolutions.net \
--cc=kilroyd@googlemail.com \
--cc=linux-wireless@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).