linux-kernel - Re: [PATCH 0/1] new module for amba axi on-chip interconnect

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20110329131453.GA17302@suse.de>
Date:	Tue, 29 Mar 2011 06:14:53 -0700
From:	Greg KH <gregkh@...e.de>
To:	Arend van Spriel <arend@...adcom.com>
Cc:	linux-kernel@...r.kernel.org, akpm@...ux-foundation.org,
	rmk+kernel@....linux.org.uk, linux-wireless@...r.kernel.org,
	devel@...uxdriverproject.org
Subject: Re: [PATCH 0/1] new module for amba axi on-chip interconnect

On Tue, Mar 29, 2011 at 11:40:18AM +0200, Arend van Spriel wrote:
> GUIDANCE NEEDED:
> This patch puts the module at proposed location. Please provide your
> guidance if there is a better location within the linux tree for this
> module.
> 
> This module has been isolated from the brcm80211 driver currently
> located in staging and provided to other drivers for chipsets using
> the AMBA AXI on-chip interconnect with ARM Device Management Plugin
> (DMP) silicon IP, which provides system discovery (chip being the
> system) and basic core function (disable, reset, etc.).
> 
> The module has previously been posted on the linux-wireless list and
> comments by Randy Dunlap have been taken in. Also the SubmitChecklist
> has been followed.
> 
> Arend van Spriel (1):
>   drivers: brcmaxi: provide amba axi functionality in separate module
> 
>  drivers/Kconfig            |    2 +
>  drivers/Makefile           |    1 +
>  drivers/brcmaxi/Kconfig    |   23 ++

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.

thanks,

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/