From: "Arend van Spriel" <arend@broadcom.com>
To: "Greg KH" <greg@kroah.com>
Cc: linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.arm.linux.org.uk,
"Michael Büsch" <mb@bu3sch.de>,
"Jonas Gorski" <jonas.gorski@gmail.com>,
arend@broadcom.com
Subject: Re: [PATCH 0/1] new module for amba axi on-chip interconnect
Date: Thu, 31 Mar 2011 13:32:08 +0200 [thread overview]
Message-ID: <op.vs7gzu193ri7v4@arend-laptop> (raw)
On Tue, Mar 29, 2011 at 06:14:53 -0700, Greg KH wrote:
> I thought this was going under drivers/staging/ What changed your mind?
> What other drivers are going to use this, I thought the current broadcom
> drivers in drivers/net/wireless were not going to need this.
Last time you asked me whether it was necessary to have this in staging.
For this module I (think I) followed the kernel coding style and tried to
cover most of the SubmitChecklist (if applicable). If I should reconsider
that is fine by me.
The request for supporting amba axi scanning was raised by Jonas Gorski on
Mon 17 Jan 2011 "Merging SSB and HND/AI support" on linux-wireless list.
He was looking for this in the context of SoC router chips offering core
discovery by so-called DMP plugin which ARM provides for SoC's using the
AMBA AXI interconnect.
Gr. AvS
--
"The most merciful thing in the world, I think, is the inability of the
human
mind to correlate all its contents." - "The Call of Cthulhu"
next reply other threads:[~2011-03-31 11:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-31 11:32 Arend van Spriel [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-03-29 9:40 Arend van Spriel
2011-03-29 13:14 ` Greg KH
2011-03-29 18:19 ` Russell King
2011-03-30 13:09 ` Arnd Bergmann
2011-03-30 17:40 ` Russell King - ARM Linux
2011-03-30 18:24 ` Arnd Bergmann
2011-03-30 19:08 ` Russell King - ARM Linux
2011-04-01 15:40 ` Arnd Bergmann
2011-03-29 18:30 ` Christoph Hellwig
2011-03-29 18:40 ` Russell King
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=op.vs7gzu193ri7v4@arend-laptop \
--to=arend@broadcom.com \
--cc=greg@kroah.com \
--cc=jonas.gorski@gmail.com \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=mb@bu3sch.de \
/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
all inboxes | Powered by JetHome®