linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "John W. Linville" <linville@tuxdriver.com>
To: Arend van Spriel <arend@broadcom.com>
Cc: "Rafał Miłecki" <zajec5@gmail.com>,
	"Michael Büsch" <mb@bu3sch.de>,
	"Brett Rudley" <brudley@broadcom.com>,
	"Henry Ptasinski" <henryp@broadcom.com>,
	"George Kashperko" <george@znau.edu.ua>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: new utility kernel module for detecting cores in newer chipsets
Date: Mon, 21 Mar 2011 11:14:22 -0400	[thread overview]
Message-ID: <20110321151422.GB3731@tuxdriver.com> (raw)
In-Reply-To: <op.vso77ddp3ri7v4@arend-laptop>

On Mon, Mar 21, 2011 at 04:05:27PM +0100, Arend van Spriel wrote:

> To summarize this, my main issue (and Michael's, I think) is with
> the dependency being imposed between ai and ssb. Having two
> completely independent modules really makes more sense.

FWIW, this approach makes the most sense to me as well.

-- 
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:[~2011-03-21 15:15 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <op.vslagcb13ri7v4@arend-laptop>
2011-03-19 12:13 ` new utility kernel module for detecting cores in newer chipsets Arend van Spriel
2011-03-20  9:55   ` Rafał Miłecki
2011-03-20 13:07     ` George Kashperko
2011-03-20 17:04       ` Arend van Spriel
     [not found] ` <1300538338.11949.12.camel@maggie>
     [not found]   ` <20110319214234.GA5152@kroah.com>
     [not found]     ` <1300573336.11949.25.camel@maggie>
     [not found]       ` <20110319234524.GA7493@kroah.com>
     [not found]         ` <op.vsmyhmei3ri7v4@arend-laptop>
     [not found]           ` <20110320145421.GA13962@kroah.com>
     [not found]             ` <op.vsnd1a1i3ri7v4@arend-laptop>
     [not found]               ` <20110320162200.GA17030@kroah.com>
     [not found]                 ` <op.vsng7q1j3ri7v4@arend-laptop>
     [not found]                   ` <20110320185216.GD19375@kroah.com>
2011-03-21 10:12                     ` Rafał Miłecki
2011-03-21 14:05                       ` Greg KH
2011-03-21 14:27                         ` Rafał Miłecki
2011-03-21 14:46                           ` Greg KH
2011-03-21 14:52                             ` Rafał Miłecki
2011-03-21 15:16                               ` Greg KH
2011-03-21 15:33                                 ` Rafał Miłecki
2011-03-21 15:05                           ` Arend van Spriel
2011-03-21 15:14                             ` John W. Linville [this message]
2011-03-21 15:30                             ` Rafał Miłecki
2011-03-21 16:25                               ` George Kashperko
2011-03-21 16:24                             ` Michael Büsch
2011-03-21 16:28                               ` Michael Büsch

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=20110321151422.GB3731@tuxdriver.com \
    --to=linville@tuxdriver.com \
    --cc=arend@broadcom.com \
    --cc=brudley@broadcom.com \
    --cc=george@znau.edu.ua \
    --cc=henryp@broadcom.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mb@bu3sch.de \
    --cc=zajec5@gmail.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 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).