linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Michael Büsch" <mb@bu3sch.de>
To: George Kashperko <george@znau.edu.ua>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [RFC] AI support (2/14 ssb helpers)
Date: Sat, 19 Feb 2011 00:29:37 +0100	[thread overview]
Message-ID: <1298071777.23801.42.camel@maggie> (raw)
In-Reply-To: <1298070945.25739.31.camel@dev.znau.edu.ua> (sfid-20110219_002424_959914_4197FDC7)

On Sat, 2011-02-19 at 01:15 +0200, George Kashperko wrote: 
> > On Fri, 2011-02-18 at 00:08 +0200, George Kashperko wrote: 
> > > 	const struct ssb_bus_ops *ops;
> > > +	const struct ssb_bus_helpers *helpers;
> > 
> > Uhm, well. "helpers"... . Seems like a pretty generic term.
> > 
> > I think this is still violating abstraction layering. Not as much
> > as your previous attempt, but still...
> > 
> > You're putting the ops structure that is supposed to abstract
> > the ssb bus into the ssb_device data structure. That should ring a bell.
> > 
> Reconsidered it already while arranging patches for Openwrt (the reason
> helpers were in device struct was to speedup access but these aint
> called often therefore they are in ssb_bus now). Also moved

I should probably note that in my opinion ssb_bus is not the right place
to put ops that are supposed to abstract the SSB bus, too. ;)
_No_ SSB structure is the right place to put an ops pointer that is
supposed to abstract the SSB bus.

-- 
Greetings Michael.


  reply	other threads:[~2011-02-18 23:29 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-17 15:58 [RFC] AI support George Kashperko
2011-02-17 22:01 ` Michael Büsch
2011-02-17 22:06   ` [RFC] AI support (1/14 ssb admatch redefine) George Kashperko
2011-02-17 22:08   ` [RFC] AI support (2/14 ssb helpers) George Kashperko
2011-02-18 22:29     ` Michael Büsch
2011-02-18 23:15       ` George Kashperko
2011-02-18 23:29         ` Michael Büsch [this message]
2011-02-18 23:27           ` George Kashperko
2011-02-17 22:10   ` [RFC] AI support (3/14 ssb irqflag mips core op) George Kashperko
2011-02-17 22:12   ` [RFC] AI support (4/14 ssb mips core irqflag treatment) George Kashperko
2011-02-17 22:14   ` [RFC] AI support (5/14 ssb core control and state helpers) George Kashperko
2011-02-17 22:16   ` [RFC] AI support (6/14 ssb propagate core control and state helpers usage) George Kashperko
2011-02-17 22:18   ` [RFC] AI support (7/14 ssb bus_check_core routine) George Kashperko
2011-02-17 22:20   ` [RFC] AI support (8/14 ssb ssb_bus_detect routine) George Kashperko
2011-02-18 22:35     ` Michael Büsch
2011-02-17 22:23   ` [RFC] AI support (9/14 ssb SB-specific bus scan routine) George Kashperko
2011-02-17 22:25   ` [RFC] AI support (10/14 ssb bus implementation-specific io unmap) George Kashperko
2011-02-17 22:27   ` [RFC] AI support (11/14 ssb separate SB-specific code) George Kashperko
2011-02-17 22:29   ` [RFC] AI support (12/14 ssb mips74k core defs) George Kashperko
2011-02-17 22:31   ` [RFC] AI support (13/14 ssb add AI support) George Kashperko
2011-02-18 22:45     ` Michael Büsch
2011-02-18 23:07       ` George Kashperko
2011-02-18 23:27         ` Michael Büsch
2011-02-18 23:42           ` George Kashperko
2011-02-18 23:54             ` Michael Büsch
2011-02-18 23:51               ` George Kashperko
2011-02-18 23:46           ` Larry Finger
2011-02-18 23:47             ` George Kashperko
2011-02-19  0:06               ` Larry Finger
2011-02-19  0:08                 ` George Kashperko
2011-02-19  0:22                   ` Larry Finger
2011-02-17 22:35   ` [RFC] AI support (14/14 ssb AI on pci host (untested)) George Kashperko
2011-02-18  2:43 ` [RFC] AI support Henry Ptasinski
2011-02-18  7:39   ` George Kashperko
2011-02-18 11:53     ` Michael Büsch
2011-02-18 12:39       ` George Kashperko
2011-02-18 22:21         ` Michael Büsch
2011-02-18 22:52           ` George Kashperko

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=1298071777.23801.42.camel@maggie \
    --to=mb@bu3sch.de \
    --cc=george@znau.edu.ua \
    --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).