| 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
| ||
|
Message-ID: <AANLkTinpLeJzYjAh2bUngWD4ZvOyy44t9+4Zs9rm2=xQ@mail.gmail.com> Date: Fri, 3 Sep 2010 19:50:33 +0200 From: Linus Walleij <linus.ml.walleij@...il.com> To: Masayuki Ohtak <masa-korg@....okisemi.com> Cc: meego-dev@...go.com, LKML <linux-kernel@...r.kernel.org>, David Brownell <dbrownell@...rs.sourceforge.net>, qi.wang@...el.com, yong.y.wang@...el.com, andrew.chih.howe.khor@...el.com, arjan@...ux.intel.com, gregkh@...e.de, Tomoya MORINAGA <morinaga526@....okisemi.com>, Grant Likely <grant.likely@...retlab.ca> Subject: Re: [MeeGo-Dev][PATCH] Topcliff: Update PCH_SPI driver to 2.6.35 2010/9/3 Grant Likely <grant.likely@...retlab.ca>: > 2010/9/3 Masayuki Ohtak <masa-korg@....okisemi.com>: >> SPI driver of Topcliff PCH > Instead, the majority of the code should be structured to handle one > and only one spi bus instance. Only at the top level pci probe, > remove and PM code should there be for() loops for setting up or > tearing down each spi bus instance one at a time. I guess an elegant way to achieve this is to have the PCI driver spawn a simple platform device for each bus. Then you can even break the driver for that platform device into its own file and all. In the MFDs we spawn child platform devices all the time, it's great fun! 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/
Powered by blists - more mailing lists