linux-kernel - Re: [PATCH] ARM: pxa: Remove unused clock_enable field from struct pxa2xx_spi

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]

Date:	Sun, 20 Sep 2015 19:36:23 +0200
From:	Robert Jarzmik <robert.jarzmik@...e.fr>
To:	Jarkko Nikula <jarkko.nikula@...ux.intel.com>
Cc:	linux-kernel@...r.kernel.org, linux-spi@...r.kernel.org,
	Russell King <linux@....linux.org.uk>,
	Mark Brown <broonie@...nel.org>,
	Philipp Zabel <philipp.zabel@...il.com>,
	Paul Parsons <lost.distance@...oo.com>,
	Daniel Mack <daniel@...que.org>,
	Haojian Zhuang <haojian.zhuang@...il.com>,
	Marek Vasut <marek.vasut@...il.com>
Subject: Re: [PATCH] ARM: pxa: Remove unused clock_enable field from struct pxa2xx_spi_master

Jarkko Nikula <jarkko.nikula@...ux.intel.com> writes:

> Use for struct pxa2xx_spi_master clock_enable field was removed years ago
> from the pxa2xx-spi driver by the commit 2f1a74e5a2de ("[ARM] pxa: make
> pxa2xx_spi driver use ssp_request()/ssp_free()").
>
> Therefore remove it from structure definition, documentation and from
> couple affected board files.
>
> Signed-off-by: Jarkko Nikula <jarkko.nikula@...ux.intel.com>
> ---
> I propose this to be merged via ARM tree. I don't see we would need to do
> other SPI related changes to struct pxa2xx_spi_master in near future (knock
> on wood).
I'll take that through the pxa/for-next tree in a couple of days, thanks.

Cheers.

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