)]}' { "log": [ { "commit": "53947027ad90542ddb2bb746e3175827c270610a", "tree": "385add6ef71095c9dba4c23ef778d92502de1086", "parents": [ "8c2676a5870ab15cbeea9f826266bc946fe3cc26" ], "author": { "name": "Keith Mannthey", "email": "kmannth@us.ibm.com", "time": "Sat Sep 30 23:27:08 2006 -0700" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@g5.osdl.org", "time": "Sun Oct 01 00:39:18 2006 -0700" }, "message": "[PATCH] hot-add-mem x86_64: use CONFIG_MEMORY_HOTPLUG_SPARSE\n\nMigate CONFIG_MEMORY_HOTPLUG to CONFIG_MEMORY_HOTPLUG_SPARSE where needed.\n\nSigned-off-by: Keith Mannthey \u003ckmannth@us.ibm.com\u003e\nCc: KAMEZAWA Hiroyuki \u003ckamezawa.hiroyu@jp.fujitsu.com\u003e\nCc: Andi Kleen \u003cak@muc.de\u003e\nSigned-off-by: Andrew Morton \u003cakpm@osdl.org\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@osdl.org\u003e\n" }, { "commit": "a5117ba7da37deb09df5eb802dace229b3fb1e9f", "tree": "eec1e160cbc11a4a1dae107ed27d92c991f5fcf6", "parents": [ "3e95637a48820ff8bedb33e6439def96ccff1de5" ], "author": { "name": "Rene Herman", "email": "rene.herman@keyaccess.nl", "time": "Tue Jun 06 23:54:02 2006 +0200" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@suse.de", "time": "Wed Jun 21 12:40:49 2006 -0700" }, "message": "[PATCH] Driver model: add ISA bus\n\nDuring the recent \"isa drivers using platform devices\" discussion it was\npointed out that (ALSA) ISA drivers ran into the problem of not having\nthe option to fail driver load (device registration rather) upon not\nfinding their hardware due to a probe() error not being passed up\nthrough the driver model. In the course of that, I suggested a seperate\nISA bus might be best; Russell King agreed and suggested this bus could\nuse the .match() method for the actual device discovery.\n\nThe attached does this. For this old non (generically) discoverable ISA\nhardware only the driver itself can do discovery so as a difference with\nthe platform_bus, this isa_bus also distributes match() up to the driver.\n\nAs another difference: these devices only exist in the driver model due\nto the driver creating them because it might want to drive them, meaning\nthat all device creation has been made internal as well.\n\nThe usage model this provides is nice, and has been acked from the ALSA\nside by Takashi Iwai and Jaroslav Kysela. The ALSA driver module_init\u0027s\nnow (for oldisa-only drivers) become:\n\nstatic int __init alsa_card_foo_init(void)\n{\n\treturn isa_register_driver(\u0026snd_foo_isa_driver, SNDRV_CARDS);\n}\n\nstatic void __exit alsa_card_foo_exit(void)\n{\n\tisa_unregister_driver(\u0026snd_foo_isa_driver);\n}\n\nQuite like the other bus models therefore. This removes a lot of\nduplicated init code from the ALSA ISA drivers.\n\nThe passed in isa_driver struct is the regular driver struct embedding a\nstruct device_driver, the normal probe/remove/shutdown/suspend/resume\ncallbacks, and as indicated that .match callback.\n\nThe \"SNDRV_CARDS\" you see being passed in is a \"unsigned int ndev\"\nparameter, indicating how many devices to create and call our methods with.\n\nThe platform_driver callbacks are called with a platform_device param;\nthe isa_driver callbacks are being called with a \"struct device *dev,\nunsigned int id\" pair directly -- with the device creation completely\ninternal to the bus it\u0027s much cleaner to not leak isa_dev\u0027s by passing\nthem in at all. The id is the only thing we ever want other then the\nstruct device * anyways, and it makes for nicer code in the callbacks as\nwell.\n\nWith this additional .match() callback ISA drivers have all options. If\nALSA would want to keep the old non-load behaviour, it could stick all\nof the old .probe in .match, which would only keep them registered after\neverything was found to be present and accounted for. If it wanted the\nbehaviour of always loading as it inadvertently did for a bit after the\nchangeover to platform devices, it could just not provide a .match() and\ndo everything in .probe() as before.\n\nIf it, as Takashi Iwai already suggested earlier as a way of following\nthe model from saner buses more closely, wants to load when a later bind\ncould conceivably succeed, it could use .match() for the prerequisites\n(such as checking the user wants the card enabled and that port/irq/dma\nvalues have been passed in) and .probe() for everything else. This is\nthe nicest model.\n\nTo the code...\n\nThis exports only two functions; isa_{,un}register_driver().\n\nisa_register_driver() register\u0027s the struct device_driver, and then\nloops over the passed in ndev creating devices and registering them.\nThis causes the bus match method to be called for them, which is:\n\nint isa_bus_match(struct device *dev, struct device_driver *driver)\n{\n struct isa_driver *isa_driver \u003d to_isa_driver(driver);\n\n if (dev-\u003eplatform_data \u003d\u003d isa_driver) {\n if (!isa_driver-\u003ematch ||\n isa_driver-\u003ematch(dev, to_isa_dev(dev)-\u003eid))\n return 1;\n dev-\u003eplatform_data \u003d NULL;\n }\n return 0;\n}\n\nThe first thing this does is check if this device is in fact one of this\ndriver\u0027s devices by seeing if the device\u0027s platform_data pointer is set\nto this driver. Platform devices compare strings, but we don\u0027t need to\ndo that with everything being internal, so isa_register_driver() abuses\ndev-\u003eplatform_data as a isa_driver pointer which we can then check here.\nI believe platform_data is available for this, but if rather not, moving\nthe isa_driver pointer to the private struct isa_dev is ofcourse fine as\nwell.\n\nThen, if the the driver did not provide a .match, it matches. If it did,\nthe driver match() method is called to determine a match.\n\nIf it did _not_ match, dev-\u003eplatform_data is reset to indicate this to\nisa_register_driver which can then unregister the device again.\n\nIf during all this, there\u0027s any error, or no devices matched at all\neverything is backed out again and the error, or -ENODEV, is returned.\n\nisa_unregister_driver() just unregisters the matched devices and the\ndriver itself.\n\nMore global points/questions...\n\n- I\u0027m introducing include/linux/isa.h. It was available but is ofcourse\na somewhat generic name. Moving more isa stuff over to it in time is\nofcourse fine, so can I have it please? :)\n\n- I\u0027m using device_initcall() and added the isa.o (dependent on\nCONFIG_ISA) after the base driver model things in the Makefile. Will\nthis do, or I really need to stick it in drivers/base/init.c, inside\n#ifdef CONFIG_ISA? It\u0027s working fine.\n\nLastly -- I also looked, a bit, into integrating with PnP. \"Old ISA\"\ncould be another pnp_protocol, but this does not seem to be a good\nmatch, largely due to the same reason platform_devices weren\u0027t -- the\ndevices do not have a life of their own outside the driver, meaning the\npnp_protocol {get,set}_resources callbacks would need to callback into\ndriver -- which again means you first need to _have_ that driver. Even\nif there\u0027s clean way around that, you only end up inventing fake but\nvalid-form PnP IDs and generally catering to the PnP layer without any\npractical advantages over this very simple isa_bus. The thing I also\nsuggested earlier about the user echoing values into /sys to set up the\nhardware from userspace first is... well, cute, but a horrible idea from\na user standpoint.\n\nComments ofcourse appreciated. Hope it\u0027s okay. As said, the usage model\nis nice at least.\n\nSigned-off-by: Rene Herman \u003crene.herman@keyaccess.nl\u003e\n" }, { "commit": "4039483fd3065920f035eed39ec59085421c0a4f", "tree": "fc89410a8cd031c3f71a7319987fa6fc9b09336c", "parents": [ "e391553222211e07dfbe2f01c413b4e6d0ae32aa" ], "author": { "name": "Michael Holzheu", "email": "holzheu@de.ibm.com", "time": "Tue May 09 12:53:49 2006 +0200" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@suse.de", "time": "Wed Jun 21 12:40:48 2006 -0700" }, "message": "[PATCH] Driver Core: Add /sys/hypervisor when needed\n\nTo have a home for all hypervisors, this patch creates /sys/hypervisor.\nA new config option SYS_HYPERVISOR is introduced, which should to be set\nby architecture dependent hypervisors (e.g. s390 or Xen).\n\nAcked-by: Martin Schwidefsky \u003cschwidefsky@de.ibm.com\u003e\nSigned-off-by: Michael Holzheu \u003cholzheu@de.ibm.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@suse.de\u003e\n" }, { "commit": "69dcc99199fe29b0a29471a3488d39d9d33b25fc", "tree": "4232ad9a782dee6abfe7fa20c95a49249195de8f", "parents": [ "66ac5a294db70aa377c0d7bbdb0c4e3ef2349b7b" ], "author": { "name": "Zhang, Yanmin", "email": "yanmin.zhang@intel.com", "time": "Fri Feb 03 03:04:36 2006 -0800" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@g5.osdl.org", "time": "Fri Feb 03 08:32:09 2006 -0800" }, "message": "[PATCH] Export cpu topology in sysfs\n\nThe patch implements cpu topology exportation by sysfs.\n\nItems (attributes) are similar to /proc/cpuinfo.\n\n1) /sys/devices/system/cpu/cpuX/topology/physical_package_id:\n\trepresent the physical package id of cpu X;\n2) /sys/devices/system/cpu/cpuX/topology/core_id:\n\trepresent the cpu core id to cpu X;\n3) /sys/devices/system/cpu/cpuX/topology/thread_siblings:\n\trepresent the thread siblings to cpu X in the same core;\n4) /sys/devices/system/cpu/cpuX/topology/core_siblings:\n\trepresent the thread siblings to cpu X in the same physical package;\n\nTo implement it in an architecture-neutral way, a new source file,\ndriver/base/topology.c, is to export the 5 attributes.\n\nIf one architecture wants to support this feature, it just needs to\nimplement 4 defines, typically in file include/asm-XXX/topology.h.\nThe 4 defines are:\n#define topology_physical_package_id(cpu)\n#define topology_core_id(cpu)\n#define topology_thread_siblings(cpu)\n#define topology_core_siblings(cpu)\n\nThe type of **_id is int.\nThe type of siblings is cpumask_t.\n\nTo be consistent on all architectures, the 4 attributes should have\ndeafult values if their values are unavailable. Below is the rule.\n\n1) physical_package_id: If cpu has no physical package id, -1 is the\ndefault value.\n\n2) core_id: If cpu doesn\u0027t support multi-core, its core id is 0.\n\n3) thread_siblings: Just include itself, if the cpu doesn\u0027t support\nHT/multi-thread.\n\n4) core_siblings: Just include itself, if the cpu doesn\u0027t support\nmulti-core and HT/Multi-thread.\n\nSo be careful when declaring the 4 defines in include/asm-XXX/topology.h.\n\nIf an attribute isn\u0027t defined on an architecture, it won\u0027t be exported.\n\nThank Nathan, Greg, Andi, Paul and Venki.\n\nThe patch provides defines for i386/x86_64/ia64.\n\nSigned-off-by: Zhang, Yanmin \u003cyanmin.zhang@intel.com\u003e\nCc: Ingo Molnar \u003cmingo@elte.hu\u003e\nCc: Nick Piggin \u003cnickpiggin@yahoo.com.au\u003e\nCc: Greg KH \u003cgreg@kroah.com\u003e\nSigned-off-by: Andrew Morton \u003cakpm@osdl.org\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@osdl.org\u003e\n" }, { "commit": "3947be1969a9ce455ec30f60ef51efb10e4323d1", "tree": "0b4b3b4c268beb7aa88cb685cce48b6bb5053c47", "parents": [ "bdc8cb984576ab5b550c8b24c6fa111a873503e3" ], "author": { "name": "Dave Hansen", "email": "haveblue@us.ibm.com", "time": "Sat Oct 29 18:16:54 2005 -0700" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@g5.osdl.org", "time": "Sat Oct 29 21:40:44 2005 -0700" }, "message": "[PATCH] memory hotplug: sysfs and add/remove functions\n\nThis adds generic memory add/remove and supporting functions for memory\nhotplug into a new file as well as a memory hotplug kernel config option.\n\nIndividual architecture patches will follow.\n\nFor now, disable memory hotplug when swsusp is enabled. There\u0027s a lot of\nchurn there right now. We\u0027ll fix it up properly once it calms down.\n\nSigned-off-by: Matt Tolentino \u003cmatthew.e.tolentino@intel.com\u003e\nSigned-off-by: Dave Hansen \u003chaveblue@us.ibm.com\u003e\nSigned-off-by: Andrew Morton \u003cakpm@osdl.org\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@osdl.org\u003e\n" }, { "commit": "07e4a3e27fe414980ddc85a358e5a56abc48b363", "tree": "eb32858e7facf8b24a2f0fc2d4e829d6ee715c09", "parents": [ "af70316af182f4716cc5eec7e0d27fc731d164bd" ], "author": { "name": "mochel@digitalimplant.org", "email": "mochel@digitalimplant.org", "time": "Mon Mar 21 10:52:54 2005 -0800" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@suse.de", "time": "Mon Jun 20 15:15:13 2005 -0700" }, "message": "[PATCH] Move device/driver code to drivers/base/dd.c\n\nThis relocates the driver binding/unbinding code to drivers/base/dd.c. This is done\nfor two reasons: One, it\u0027s not code related to the bus_type itself; it uses some from\nthat, some from devices, and some from drivers. And Two, it will make it easier to do\nsome of the upcoming lock removal on that code..\n\nSigned-off-by: Patrick Mochel \u003cmochel@digitalimplant.org\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@suse.de\u003e\n" }, { "commit": "cd987d38cc59053e0bab8150ffaca33b109067f3", "tree": "68cf99616bd548bff80ca12f37912d9cc4b31edd", "parents": [ "2fc68447df5c76cf254037047b4b02551bd5d760" ], "author": { "name": "gregkh@suse.de", "email": "gregkh@suse.de", "time": "Wed Mar 23 11:12:38 2005 -0800" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@suse.de", "time": "Mon Jun 20 15:15:11 2005 -0700" }, "message": "[PATCH] class: remove class_simple code, as no one in the tree is using it anymore.\n\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@suse.de\u003e\n" }, { "commit": "0b405a0f7e4d4d18fd1fe46ddf5ff465443036ab", "tree": "49d74df6eddfdd095c650e0af34cde7f4548a2d5", "parents": [ "82428b62aa6294ea640c7e920a9224ecaf46db65" ], "author": { "name": "David Brownell", "email": "david-b@pacbell.net", "time": "Thu May 12 12:06:27 2005 -0700" }, "committer": { "name": "Greg KH", "email": "gregkh@suse.de", "time": "Tue May 17 14:54:55 2005 -0700" }, "message": "[PATCH] Driver Core: remove driver model detach_state\n\nThe driver model has a \"detach_state\" mechanism that:\n\n - Has never been used by any in-kernel drive;\n - Is superfluous, since driver remove() methods can do the same thing;\n - Became buggy when the suspend() parameter changed semantics and type;\n - Could self-deadlock when called from certain suspend contexts;\n - Is effectively wasted documentation, object code, and headspace.\n\nThis removes that \"detach_state\" mechanism; net code shrink, as well\nas a per-device saving in the driver model and sysfs.\n\nSigned-off-by: David Brownell \u003cdbrownell@users.sourceforge.net\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@suse.de\u003e\n" }, { "commit": "1da177e4c3f41524e886b7f1b8a0c1fc7321cac2", "tree": "0bba044c4ce775e45a88a51686b5d9f90697ea9d", "parents": [], "author": { "name": "Linus Torvalds", "email": "torvalds@ppc970.osdl.org", "time": "Sat Apr 16 15:20:36 2005 -0700" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@ppc970.osdl.org", "time": "Sat Apr 16 15:20:36 2005 -0700" }, "message": "Linux-2.6.12-rc2\n\nInitial git repository build. I\u0027m not bothering with the full history,\neven though we have it. We can create a separate \"historical\" git\narchive of that later if we want to, and in the meantime it\u0027s about\n3.2GB when imported into git - space that would just make the early\ngit days unnecessarily complicated, when we don\u0027t have a lot of good\ninfrastructure for it.\n\nLet it rip!\n" } ] }