linux-kernel - Re: [PATCH 5/5] spi: amba_pl022: Remove unused fields from pl022_config

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 for Android: free password hash cracker in your pocket

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

Message-ID: <AANLkTimNnA=tNCE7pLiibwB66R86dNmCDpCuQMkTvw9J@mail.gmail.com>
Date:	Mon, 13 Sep 2010 15:22:16 +0200
From:	Linus Walleij <linus.ml.walleij@...il.com>
To:	wellsk40@...il.com
Cc:	spi-devel-general@...ts.sourceforge.net, sameo@...ux.intel.com,
	rabin.vincent@...ricsson.com, srinidhi.kasagar@...ricsson.com,
	linux-kernel@...r.kernel.org, linux@....linux.org.uk,
	u.kleine-koenig@...gutronix.de,
	linux-arm-kernel@...ts.infradead.org, tj@...nel.org,
	grant.likely@...retlab.ca, Lukasz.Baj@...to.com,
	quentinyang05@...il.com
Subject: Re: [PATCH 5/5] spi: amba_pl022: Remove unused fields from pl022_config_chip

2010/9/10  <wellsk40@...il.com>:

> From: Kevin Wells <wellsk40@...il.com>
>
> Some of the fields in the pl022_config_chip structure are no
> longer needed with the spi->mode updates. These fields have been
> removed.

I think you have to do a more thorough patch:

drivers/spi/amba-pl022.c: In function 'verify_controller_parameters':
drivers/spi/amba-pl022.c:1598: error: 'struct pl022_config_chip' has
no member named 'lbm'
drivers/spi/amba-pl022.c:1599: error: 'struct pl022_config_chip' has
no member named 'lbm'
drivers/spi/amba-pl022.c:1629: error: 'struct pl022_config_chip' has
no member named 'endian_rx'
(... etc)

Yours,
Linus Walleij
--
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/