All of lore.kernel.org
 help / color / mirror / Atom feed
From: "John W. Linville" <linville@tuxdriver.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Zhu Yi <yi.zhu@intel.com>, drago01 <drago01@gmail.com>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	"Ortiz, Samuel" <samuel.ortiz@intel.com>
Subject: Re: [PATCH 1/2] wireless: move some utility functions from mac80211 to cfg80211
Date: Thu, 21 May 2009 09:38:40 -0400	[thread overview]
Message-ID: <20090521133839.GA2744@tuxdriver.com> (raw)
In-Reply-To: <1242897719.5471.1.camel@johannes.local>

On Thu, May 21, 2009 at 11:21:59AM +0200, Johannes Berg wrote:
> On Thu, 2009-05-21 at 15:09 +0800, Zhu Yi wrote:
> 
> > > Isn't lib80211 a better place for those ?
> > > Its purpose is sharing code between fullmac and softmac drivers.
> > 
> > These functions are moved from mac80211 which currently doesn't link
> > with lib80211. Johannes might have more to comment.
> 
> Yeah, lib80211's stated purpose is to share code, but on the other hand
> code that mac80211 and fullmac drivers may need seems better suited in
> cfg80211 since lib80211 also ships a large code bit of crypto routines
> etc. that are just useless for this and mac80211.

The crypto stuff is mostly in separate modules.

I would rather see these in lib80211, but I'll work that out myself.

John
-- 
John W. Linville		Someday the world will need a hero, and you
linville@tuxdriver.com			might be all we have.  Be ready.

  reply	other threads:[~2009-05-21 13:45 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-21  2:18 [Announce] Intel Wireless Multicomm 3200 WiFi driver Zhu Yi
2009-05-21  2:18 ` [PATCH 1/2] wireless: move some utility functions from mac80211 to cfg80211 Zhu Yi
2009-05-21  2:19   ` [PATCH 2/2] iwmc3200wifi: Add new Intel Wireless Multicomm 802.11 driver Zhu Yi
2009-05-21  2:54     ` Luis R. Rodriguez
2009-05-21  3:13       ` Zhu Yi
2009-05-21  7:12   ` [PATCH 1/2] wireless: move some utility functions from mac80211 to cfg80211 drago01
2009-05-21  7:09     ` Zhu Yi
2009-05-21  9:21       ` Johannes Berg
2009-05-21 13:38         ` John W. Linville [this message]
2009-05-21 13:56           ` Johannes Berg
2009-05-21 14:10             ` Gábor Stefanik
2009-05-21 14:41             ` John W. Linville
2009-05-21 14:54               ` Johannes Berg
2009-05-21  9:32   ` Johannes Berg
2009-05-21 11:53     ` Zhu, Yi
2009-05-21 16:10 ` [Announce] Intel Wireless Multicomm 3200 WiFi driver Johannes Berg
2009-05-21 17:54   ` Gábor Stefanik
2009-05-21 17:57     ` Johannes Berg
2009-05-21 18:23       ` Gábor Stefanik
2009-05-26 22:24 ` Luis R. Rodriguez
2009-05-31  2:17   ` Zhu Yi
2009-05-31  6:27     ` Luis R. Rodriguez
2009-05-31  6:42       ` Zhu Yi
2009-05-31 12:10         ` Maxim Levitsky
2009-05-31 12:20           ` Gábor Stefanik
2009-06-01  1:29           ` Zhu Yi
2009-06-01 22:52             ` Luis R. Rodriguez
2009-06-02  7:36               ` Zhu Yi
2009-06-01 23:00         ` Luis R. Rodriguez
2009-06-02  7:42           ` Zhu Yi
2009-06-02 16:53             ` Luis R. Rodriguez

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=20090521133839.GA2744@tuxdriver.com \
    --to=linville@tuxdriver.com \
    --cc=drago01@gmail.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=samuel.ortiz@intel.com \
    --cc=yi.zhu@intel.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.