linux-kernel - Re: [patch 09/14] Convert from class

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: <200708231403.52846.david-b@pacbell.net>
Date:	Thu, 23 Aug 2007 14:03:52 -0700
From:	David Brownell <david-b@...bell.net>
To:	Tony Jones <tonyj@...e.de>
Cc:	linux-kernel@...r.kernel.org, kay.sievers@...y.org
Subject: Re: [patch 09/14] Convert from class_device to device for SPI

On Tuesday 21 August 2007, Tony Jones wrote:
> I believe this is the necessary documentation changes.

Thanks.  I have an update, plus updates for the mmc_spi
driver (now in MM) which you didn't update.

By the way, it's worth noting an incompatibility introduced
through these conversions and CONFIG_SYSFS_DEPRECATED=n:

 - previously .../controller/spi_master:spi2 would be a
   symlink to /sys/class/spi_master/spi2

 - now, /sys/class/spi_master/spi2 is a symlink to
   .../controller/spi_master (with DEPRECATED=n).

The symlink direction is just noise ... the issue is that with
this approach it's no longer possible to have one controller
handle multiple SPI busses!  A fix would involve maintaining
the original "spi_master:spi2" name.

I don't happen to know of such a controller, and one would
surprise me a bit.  Exactly like the fact that several I2C
adapters work that way was a surprise:  one PCI function
controlling several different I2C busses, rather than one
function per bus.

- Dave

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