All of lore.kernel.org
 help / color / mirror / Atom feed
From: "John W. Linville" <linville@tuxdriver.com>
To: Harvey Harrison <harvey.harrison@gmail.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [RFC PATCH 1/4] lib80211: absorb crypto bits from net/ieee80211
Date: Wed, 12 Nov 2008 13:28:14 -0500	[thread overview]
Message-ID: <20081112182814.GD2411@tuxdriver.com> (raw)
In-Reply-To: <1226513943.16649.0.camel@brick>

On Wed, Nov 12, 2008 at 10:19:03AM -0800, Harvey Harrison wrote:
> On Wed, 2008-11-12 at 13:02 -0500, John W. Linville wrote:
> > On Wed, Nov 12, 2008 at 08:48:34AM -0800, Harvey Harrison wrote:
> > > On Tue, 2008-11-11 at 16:51 -0500, John W. Linville wrote:
> > > > These bits are shared already between ipw2x00 and hostap, and could
> > > > probably be shared both more cleanly and with other drivers.  This
> > > > commit simply relocates the code to lib80211 and adjusts the drivers
> > > > appropriately.
> > > > 
> > > > Signed-off-by: John W. Linville <linville@tuxdriver.com>
> > > > ---
> > > 
> > > Wouldn't it have been better to start from the mac80211 crypto bits
> > > as lib80211 and modify hostap/ipw2x00 to use the 'new' lib80211
> > > crypto bits?
> > 
> > I'm sorry, but you forgot to attach your patches...
> > 
> 
> I will if it's desired, I just wanted to know if there was a particular
> reason for going this way.

Those bits are already shared between ieee80211 and the hostap driver.
Unfortunately, they are not shared with a clean API.  I don't think
hacking on mac80211's crypto code is worthwhile until these drivers
are given a bit more discipline in this area.  IMHO, this is the
better way to start.

Perhaps you should find something more helpful to do instead.

John
-- 
John W. Linville		Linux should be at the core
linville@tuxdriver.com			of your literate lifestyle.

  reply	other threads:[~2008-11-12 18:31 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-11 21:51 [RFC PATCH 1/4] lib80211: absorb crypto bits from net/ieee80211 John W. Linville
2008-11-11 21:51 ` [RFC PATCH 2/4] lib80211: consolidate crypt init routines John W. Linville
2008-11-11 21:51   ` [RFC PATCH 3/4] ipw2x00: relocate ipw2100/ipw2200 to common directory John W. Linville
2008-11-11 21:51     ` [RFC PATCH 4/4] net/ieee80211 -> drivers/net/ipw2x00/libipw_* rename John W. Linville
2008-11-11 22:22       ` Michael Buesch
2008-11-11 23:21         ` John W. Linville
2008-11-12  3:27           ` Julian Calaby
2008-11-12 10:29             ` Michael Buesch
2008-11-12 10:39               ` Julian Calaby
2008-11-12 16:48 ` [RFC PATCH 1/4] lib80211: absorb crypto bits from net/ieee80211 Harvey Harrison
2008-11-12 18:02   ` John W. Linville
2008-11-12 18:19     ` Harvey Harrison
2008-11-12 18:28       ` John W. Linville [this message]
2008-11-12 18:35         ` John W. Linville

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=20081112182814.GD2411@tuxdriver.com \
    --to=linville@tuxdriver.com \
    --cc=harvey.harrison@gmail.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 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.