linux-kernel - adding bits_per_word to struct spi_board_info to mirror struct 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-next>] [day] [month] [year] [list]

Message-ID: <8bd0f97a0704250305qe6175cdm8e1a0cd7844f67bc@mail.gmail.com>
Date:	Wed, 25 Apr 2007 06:05:06 -0400
From:	"Mike Frysinger" <vapier.adi@...il.com>
To:	dbrownell@...rs.sourceforge.net
Cc:	spi-devel-general@...ts.sourceforge.net,
	"Linux Kernel Mailing List" <linux-kernel@...r.kernel.org>,
	"Wu, Bryan" <Bryan.Wu@...log.com>
Subject: adding bits_per_word to struct spi_board_info to mirror struct spi_device

the spi_device structure has a bits_per_word so that you can change
the value on a per-device setting, yet the spi_board_info structure
does not ... this means that the bus-specific structure has to have a
bits_per_word member which the spi bus driver will copy into the spi
device bits_per_word member

is there something obvious i'm missing ?  seems to me that if the
generic spi framework respects bits_per_word on a per-spi device
basis, then it should be exposed in the generic info structure so that
the setting can be tracked in the boards file ...
-mike
-
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/