From: "Arend van Spriel" <arend@broadcom.com>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: "Arnd Bergmann" <arnd@arndb.de>,
"George Kashperko" <george@znau.edu.ua>,
"Hauke Mehrtens" <hauke@hauke-m.de>,
"Russell King" <rmk@arm.linux.org.uk>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"Jonas Gorski" <jonas.gorski@gmail.com>,
"b43-dev@lists.infradead.org" <b43-dev@lists.infradead.org>,
"Greg KH" <greg@kroah.com>, "Andy Botting" <andy@andybotting.com>,
"Larry Finger" <Larry.Finger@lwfinger.net>
Subject: AXI driver status => previously: Re: Could I (ab)use bus (struct bus_type) for virtual Broadcom bus?
Date: Thu, 5 May 2011 14:33:35 +0200 [thread overview]
Message-ID: <4DC2991F.6030703@broadcom.com> (raw)
In-Reply-To: <BANLkTinMe-KedeOAiQYES-LCC2O4BoE28w@mail.gmail.com>
On 04/20/2011 09:29 AM, Rafał Miłecki wrote:
> I do not register that exceptional devices in my code.
Hi Rafał,
There has been some radio silence on the subject of the (bcm)axi driver.
I was getting a feeling that my concerns were almost all out of the way
in latest emails I got from Arnd and/or Jonas. Do you have an update of
what plans you have with this module.
Gr. AvS
next prev parent reply other threads:[~2011-05-05 12:33 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-14 11:28 Could I (ab)use bus (struct bus_type) for virtual Broadcom bus? Rafał Miłecki
2011-04-14 11:43 ` George Kashperko
2011-04-14 12:04 ` Rafał Miłecki
2011-04-14 12:34 ` Hauke Mehrtens
2011-04-14 13:07 ` Rafał Miłecki
2011-04-14 13:15 ` George Kashperko
2011-04-14 13:45 ` Rafał Miłecki
2011-04-15 18:36 ` George Kashperko
2011-04-15 19:21 ` Rafał Miłecki
2011-04-15 19:42 ` George Kashperko
2011-04-15 19:52 ` Rafał Miłecki
2011-04-15 19:56 ` Peter Stuge
2011-04-16 14:00 ` Rafał Miłecki
2011-04-16 14:13 ` Jonas Gorski
2011-04-15 19:50 ` George Kashperko
2011-04-17 17:38 ` Arnd Bergmann
2011-04-18 12:19 ` Rafał Miłecki
2011-04-18 14:19 ` Arnd Bergmann
2011-04-18 14:31 ` Rafał Miłecki
2011-04-18 15:35 ` George Kashperko
2011-04-18 15:53 ` Rafał Miłecki
2011-04-18 16:48 ` George Kashperko
2011-04-19 13:46 ` Arnd Bergmann
2011-04-19 13:58 ` Arend van Spriel
2011-04-19 14:02 ` Greg KH
2011-04-20 6:39 ` Arend van Spriel
2011-04-20 6:44 ` Arnd Bergmann
2011-04-19 14:20 ` Rafał Miłecki
2011-04-19 14:35 ` Arnd Bergmann
2011-04-20 7:16 ` Arend van Spriel
2011-04-20 7:26 ` Arnd Bergmann
2011-04-20 7:57 ` Arend van Spriel
2011-04-20 7:29 ` Rafał Miłecki
2011-05-05 12:33 ` Arend van Spriel [this message]
2011-05-05 12:48 ` AXI driver status => previously: " Rafał Miłecki
2011-05-05 12:54 ` Arend van Spriel
2011-04-14 13:03 ` 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=4DC2991F.6030703@broadcom.com \
--to=arend@broadcom.com \
--cc=Larry.Finger@lwfinger.net \
--cc=andy@andybotting.com \
--cc=arnd@arndb.de \
--cc=b43-dev@lists.infradead.org \
--cc=george@znau.edu.ua \
--cc=greg@kroah.com \
--cc=hauke@hauke-m.de \
--cc=jonas.gorski@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=rmk@arm.linux.org.uk \
--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).