From: "John W. Linville" <linville@tuxdriver.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Ivo van Doorn <ivdoorn@gmail.com>, Jiri Benc <jbenc@suse.cz>,
linux-wireless@vger.kernel.org
Subject: Re: [PATCH v2] d80211: Add software sequence support
Date: Thu, 15 Feb 2007 12:41:43 -0500 [thread overview]
Message-ID: <20070215174143.GA6300@tuxdriver.com> (raw)
In-Reply-To: <1171557724.5220.30.camel@johannes.berg>
On Thu, Feb 15, 2007 at 05:42:04PM +0100, Johannes Berg wrote:
> Then the driver can just call it whenever it needs the sequence number
> for a frame. It'll need to be a bit smart about fragmentation but I
> think that's ok.
>
> I may be radical, but I think that a lot of things hardware can do
> belong into library functions the driver can use instead of cluttering
> the stack with it.
I'm inclined to agree, FWIW...
--
John W. Linville
linville@tuxdriver.com
next prev parent reply other threads:[~2007-02-15 18:08 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-14 13:23 [PATCH v2] d80211: Add software sequence support Ivo van Doorn
2007-02-15 16:42 ` Johannes Berg
2007-02-15 17:41 ` John W. Linville [this message]
2007-02-15 18:54 ` Ivo Van Doorn
2007-02-15 19:02 ` Michael Wu
2007-02-15 19:11 ` Jiri Benc
2007-02-15 19:22 ` Michael Wu
2007-02-15 20:04 ` Jouni Malinen
2007-02-15 19:09 ` Jiri Benc
2007-02-15 20:48 ` Michael Wu
2007-02-15 20:57 ` Jiri Benc
2007-02-15 22:18 ` Ivo Van Doorn
2007-02-16 12:03 ` Jiri Benc
2007-02-16 12:25 ` Ivo van Doorn
2007-02-16 12:58 ` Jiri Benc
2007-02-16 14:29 ` Ivo van Doorn
2007-02-16 21:14 ` Johannes Berg
2007-02-16 22:07 ` Ivo van Doorn
2007-02-16 22:12 ` Johannes Berg
2007-02-19 19:40 ` Jiri Benc
2007-02-19 19:52 ` Johannes Berg
2007-03-10 14:38 ` Ivo van Doorn
2007-03-10 17:51 ` Michael Wu
2007-03-10 19:01 ` Ivo van Doorn
2007-03-10 19:21 ` [PATCH v3] " Ivo van Doorn
2007-03-10 19:32 ` Michael Buesch
2007-03-10 23:25 ` Ivo van Doorn
2007-03-23 17:52 ` Jiri Benc
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=20070215174143.GA6300@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=ivdoorn@gmail.com \
--cc=jbenc@suse.cz \
--cc=johannes@sipsolutions.net \
--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).