linux-kernel - Re: SPI: bcm63xx_dev

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: <CAOiHx=nHf+rRGsw_pvSwxKn5VE9QYvCvy_p6j1ETf9HSHBgUNQ@mail.gmail.com>
Date:	Thu, 12 Jul 2012 23:26:42 +0200
From:	Jonas Gorski <jonas.gorski@...il.com>
To:	Paul Bolle <pebolle@...cali.nl>
Cc:	Grant Likely <grant.likely@...retlab.ca>,
	spi-devel-general@...ts.sourceforge.net,
	linux-kernel@...r.kernel.org,
	Florian Fainelli <florian@...nwrt.org>
Subject: Re: SPI: bcm63xx_dev_spi.h

On 12 July 2012 22:55, Paul Bolle <pebolle@...cali.nl> wrote:
> 0) Commit b42dfed83d95a3c9e9cbd708f1993a7474abb79a ("spi: add Broadcom
> BCM63xx SPI controller driver") added drivers/spi/spi-bcm63xx.c to the
> mainline tree. That file includes bcm63xx_dev_spi.h.
>
> 1) bcm63xx_dev_spi.h is not part of the current tree, and, as far as I
> can tell, has actually never been part of the tree. So it seems that
> this driver could never be built using the mainline tree since it got
> added (in v3.4).
>
> 2) What's the current status of this header?

It currently sits in Ralf Baechle's queue and waits for the merge window:

http://git.linux-mips.org/?p=ralf/upstream-sfr.git;a=commit;h=435f920f35e90b4681e68002d2e2f6724b0c21b7


Jonas
--
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/