)]}' { "log": [ { "commit": "bc3b2d7fb9b014d75ebb79ba371a763dbab5e8cf", "tree": "b0fd4e724bdb1c0a1783616614ae5a9dec1cfa5c", "parents": [ "d9b9384215e17c68d7b6bd05d6fa409e5d4140d7" ], "author": { "name": "Paul Gortmaker", "email": "paul.gortmaker@windriver.com", "time": "Fri Jul 15 11:47:34 2011 -0400" }, "committer": { "name": "Paul Gortmaker", "email": "paul.gortmaker@windriver.com", "time": "Mon Oct 31 19:30:30 2011 -0400" }, "message": "net: Add export.h for EXPORT_SYMBOL/THIS_MODULE to non-modules\n\nThese files are non modular, but need to export symbols using\nthe macros now living in export.h -- call out the include so\nthat things won\u0027t break when we remove the implicit presence\nof module.h from everywhere.\n\nSigned-off-by: Paul Gortmaker \u003cpaul.gortmaker@windriver.com\u003e\n" }, { "commit": "88393161210493e317ae391696ee8ef463cb3c23", "tree": "6ec81a50d0e8174b415d83948b48cbabd7e54ddb", "parents": [ "932fb06b0898f5883200f1da2e00075f0d70ba9c" ], "author": { "name": "Thomas Weber", "email": "swirl@gmx.li", "time": "Tue Mar 16 11:47:56 2010 +0100" }, "committer": { "name": "Jiri Kosina", "email": "jkosina@suse.cz", "time": "Tue Mar 16 11:47:56 2010 +0100" }, "message": "Fix typos in comments\n\n[Ss]ytem \u003d\u003e [Ss]ystem\nudpate \u003d\u003e update\nparamters \u003d\u003e parameters\norginal \u003d\u003e original\n\nSigned-off-by: Thomas Weber \u003cswirl@gmx.li\u003e\nAcked-by: Randy Dunlap \u003crdunlap@xenotime.net\u003e\nSigned-off-by: Jiri Kosina \u003cjkosina@suse.cz\u003e\n" }, { "commit": "b54452b07a7b1b8cc1385edba3ef2ef6d4679d5a", "tree": "c8a7271b14c4cd9e0dc22a5d0a3bed9e79c88e36", "parents": [ "3ffe533c87281b68d469b279ff3a5056f9c75862" ], "author": { "name": "Alexey Dobriyan", "email": "adobriyan@gmail.com", "time": "Thu Feb 18 08:14:31 2010 +0000" }, "committer": { "name": "David S. Miller", "email": "davem@davemloft.net", "time": "Thu Feb 18 14:30:18 2010 -0800" }, "message": "const: struct nla_policy\n\nMake remaining netlink policies as const.\nFixup coding style where needed.\n\nSigned-off-by: Alexey Dobriyan \u003cadobriyan@gmail.com\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\n" }, { "commit": "f64f9e719261a87818dd192a3a2352e5b20fbd0f", "tree": "b2d5cbaef3df615295f6061d8c4d6a912690556c", "parents": [ "152b6a62aea2d43359dd37004e9c218bf7bdeb3b" ], "author": { "name": "Joe Perches", "email": "joe@perches.com", "time": "Sun Nov 29 16:55:45 2009 -0800" }, "committer": { "name": "David S. Miller", "email": "davem@davemloft.net", "time": "Sun Nov 29 16:55:45 2009 -0800" }, "message": "net: Move \u0026\u0026 and || to end of previous line\n\nNot including net/atm/\n\nCompiled tested x86 allyesconfig only\nAdded a \u003e 80 column line or two, which I ignored.\nExisting checkpatch plaints willfully, cheerfully ignored.\n\nSigned-off-by: Joe Perches \u003cjoe@perches.com\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\n" }, { "commit": "81d3f905389e22bb9a5176b9309c3f451c260e1a", "tree": "8b7cc14d8c19d63f4d7a3e1d38cf49defc769620", "parents": [ "de9315fa3a35ebe587cc1a1c88655d095846785e" ], "author": { "name": "Inaky Perez-Gonzalez", "email": "inaky@linux.intel.com", "time": "Sat Oct 03 16:51:02 2009 +0900" }, "committer": { "name": "Inaky Perez-Gonzalez", "email": "inaky@linux.intel.com", "time": "Mon Oct 19 15:56:14 2009 +0900" }, "message": "wimax: allow WIMAX_RF_QUERY calls when state is still uninitialized\n\nUntil now, calls to wimax_rfkill() will be blocked until the device is\nat least past the WIMAX_ST_UNINITIALIZED state, return -ENOMEDIUM when\nthe device is in the WIMAX_ST_DOWN state.\n\nIn parallel, wimax-tools would issue a wimax_rfkill(WIMAX_RF_QUERY)\ncall right after opening a handle with wimaxll_open() as means to\nverify if the interface is really a WiMAX interface [newer kernel\nversion will have a call specifically for this].\n\nThe combination of these two facts is that in some cases, before the\ndriver has finalized initializing its device\u0027s firmware, a\nwimaxll_open() call would fail, when it should not.\n\nThus, change the wimax_rfkill() code to allow queries when the device\nis in WIMAX_ST_UNINITIALIZED state.\n\nSigned-off-by: Inaky Perez-Gonzalez \u003cinaky@linux.intel.com\u003e\n" }, { "commit": "c29eaf3faef7547ba72355bac44e9ca6ffdaee39", "tree": "aa622b0943b0aef40b449379dff1561770357af5", "parents": [ "5b45bfe5010ae1ddaac463d1bcdb141a4ff4ff66" ], "author": { "name": "Inaky Perez-Gonzalez", "email": "inaky@linux.intel.com", "time": "Thu Aug 27 17:54:53 2009 -0700" }, "committer": { "name": "Inaky Perez-Gonzalez", "email": "inaky@linux.intel.com", "time": "Mon Oct 19 15:55:34 2009 +0900" }, "message": "wimax: indicate initial SW rfkill state is \"blocked\"\n\nThe WiMAX stack assumes that all WiMAX devices are SW OFF when they\nare initialized. The recent changes in the RFKILL stack thus cause an\ninitial call after rfkill_register(), because by default, rfkill\nconsiders devices to be SW ON upon registration.\n\nSo call rfkill_init_sw_state() to set it to SW OFF so\nrfkill_register() doesn\u0027t do that unnecessary step.\n\nSigned-off-by: Inaky Perez-Gonzalez \u003cinaky@linux.intel.com\u003e\n" }, { "commit": "d2f4c10544231c3681f937a1e511f4780b4b39af", "tree": "0805e8ce546a5b5edb5594302b9151c6dd8d5b8a", "parents": [ "0bcfc5ef016e8217709c65c5a7335e40ceabc99c" ], "author": { "name": "Inaky Perez-Gonzalez", "email": "inaky@linux.intel.com", "time": "Thu Jun 11 11:12:48 2009 -0700" }, "committer": { "name": "Inaky Perez-Gonzalez", "email": "inaky@linux.intel.com", "time": "Thu Jun 11 11:12:48 2009 -0700" }, "message": "wimax: fix warning caused by not checking retval of rfkill_set_hw_state()\n\nCaused by an API update. The return value can be safely ignored, as\nthere is notthing we can do with it.\n\nSigned-off-by: Inaky Perez-Gonzalez \u003cinaky@linux.intel.com\u003e\n" }, { "commit": "19d337dff95cbf76edd3ad95c0cee2732c3e1ec5", "tree": "33326eeb09cb9664cc8427a5dc7cd2b08b5a57c3", "parents": [ "0f6399c4c525b518644a9b09f8d6fb125a418c4d" ], "author": { "name": "Johannes Berg", "email": "johannes@sipsolutions.net", "time": "Tue Jun 02 13:01:37 2009 +0200" }, "committer": { "name": "John W. Linville", "email": "linville@tuxdriver.com", "time": "Wed Jun 03 14:06:13 2009 -0400" }, "message": "rfkill: rewrite\n\nThis patch completely rewrites the rfkill core to address\nthe following deficiencies:\n\n * all rfkill drivers need to implement polling where necessary\n rather than having one central implementation\n\n * updating the rfkill state cannot be done from arbitrary\n contexts, forcing drivers to use schedule_work and requiring\n lots of code\n\n * rfkill drivers need to keep track of soft/hard blocked\n internally -- the core should do this\n\n * the rfkill API has many unexpected quirks, for example being\n asymmetric wrt. alloc/free and register/unregister\n\n * rfkill can call back into a driver from within a function the\n driver called -- this is prone to deadlocks and generally\n should be avoided\n\n * rfkill-input pointlessly is a separate module\n\n * drivers need to #ifdef rfkill functions (unless they want to\n depend on or select RFKILL) -- rfkill should provide inlines\n that do nothing if it isn\u0027t compiled in\n\n * the rfkill structure is not opaque -- drivers need to initialise\n it correctly (lots of sanity checking code required) -- instead\n force drivers to pass the right variables to rfkill_alloc()\n\n * the documentation is hard to read because it always assumes the\n reader is completely clueless and contains way TOO MANY CAPS\n\n * the rfkill code needlessly uses a lot of locks and atomic\n operations in locked sections\n\n * fix LED trigger to actually change the LED when the radio state\n changes -- this wasn\u0027t done before\n\nTested-by: Alan Jenkins \u003calan-jenkins@tuffmail.co.uk\u003e\nSigned-off-by: Henrique de Moraes Holschuh \u003chmh@hmh.eng.br\u003e [thinkpad]\nSigned-off-by: Johannes Berg \u003cjohannes@sipsolutions.net\u003e\nSigned-off-by: John W. Linville \u003clinville@tuxdriver.com\u003e\n" }, { "commit": "621cac85297de5ba655e3430b007dd2e0da91da6", "tree": "6193ecf0966094bb744fb4238191bcab03a3cdef", "parents": [ "c1c6b14b22af0f85d05a70405dc3fba5de840c7b" ], "author": { "name": "Johannes Berg", "email": "johannes@sipsolutions.net", "time": "Fri Mar 27 14:14:31 2009 +0100" }, "committer": { "name": "John W. Linville", "email": "linville@tuxdriver.com", "time": "Wed Apr 22 16:54:27 2009 -0400" }, "message": "rfkill: remove user_claim stuff\n\nAlmost all drivers do not support user_claim, so remove it\ncompletely and always report -EOPNOTSUPP to userspace. Since\nuserspace cannot really drive rfkill _anyway_ (due to the\nodd restrictions imposed by the documentation) having this\ncode is just pointless.\n\nSigned-off-by: Johannes Berg \u003cjohannes@sipsolutions.net\u003e\nSigned-off-by: John W. Linville \u003clinville@tuxdriver.com\u003e\n" }, { "commit": "c1c6b14b22af0f85d05a70405dc3fba5de840c7b", "tree": "f60031dacc62cbab1212856230ce933559b6ea05", "parents": [ "f4a11bb0c2d5968ea35f95bdbabdd453862f202a" ], "author": { "name": "Johannes Berg", "email": "johannes@sipsolutions.net", "time": "Mon Mar 30 11:32:46 2009 +0200" }, "committer": { "name": "John W. Linville", "email": "linville@tuxdriver.com", "time": "Wed Apr 22 16:54:27 2009 -0400" }, "message": "rfkill: remove deprecated state constants\n\nI only did superficial review, but these constants are stupid\nto have and without proper warnings nobody will review the\ncode anyway, no amount of shouting will help.\n\nAlso fix wimax to use correct states.\n\nSigned-off-by: Johannes Berg \u003cjohannes@sipsolutions.net\u003e\nSigned-off-by: John W. Linville \u003clinville@tuxdriver.com\u003e\n" }, { "commit": "a2e9da4b09c99857080afd2e8143f70bc03ebe9b", "tree": "ade1399ed3785a16330d67d97a214bcad6fe4bf3", "parents": [ "71f78afd67ca51d3656ba45aea293d6e2a27c8bc" ], "author": { "name": "Inaky Perez-Gonzalez", "email": "inaky@linux.intel.com", "time": "Thu Jan 08 11:08:01 2009 -0800" }, "committer": { "name": "David S. Miller", "email": "davem@davemloft.net", "time": "Thu Jan 08 11:08:01 2009 -0800" }, "message": "wimax: testing for rfkill support should also test for CONFIG_RFKILL_MODULE\n\nCurrent WiMAX rfkill code is missing the case where rfkill is compiled\nin as modules and works only when rfkill is compiled in. This is not\ncorrect. Fixed to test for CONFIG_RFKILL or CONFIG_RKILL_MODULE.\n\nSigned-off-by: Inaky Perez-Gonzalez \u003cinaky@linux.intel.com\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\n" }, { "commit": "3e65646bb12be03b14dff53907391095a52d5f49", "tree": "5ab2961f02a2d078990e69584af81b1197fb2392", "parents": [ "3efb40c2c6eea315abcf19239c15d088e2498299" ], "author": { "name": "Inaky Perez-Gonzalez", "email": "inaky@linux.intel.com", "time": "Sat Dec 20 16:57:38 2008 -0800" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@suse.de", "time": "Wed Jan 07 10:00:17 2009 -0800" }, "message": "wimax: basic API: kernel/user messaging, rfkill and reset\n\nImplements the three basic operations provided by the stack\u0027s control\ninterface to WiMAX devices:\n\n- Messaging channel between user space and driver/device\n\n This implements a direct communication channel between user space\n and the driver/device, by which free form messages can be sent back\n and forth.\n\n This is intended for device-specific features, vendor quirks, etc.\n\n- RF-kill framework integration\n\n Provide most of the RF-Kill integration for WiMAX drivers so that\n all device drivers have to do is after wimax_dev_add() is call\n wimax_report_rfkill_{hw,sw}() to update initial state and then every\n time it changes.\n\n Provides wimax_rfkill() for the kernel to call to set software\n RF-Kill status and/or query current hardware and software switch\n status.\n\n Exports wimax_rfkill() over generic netlink to user space.\n\n- Reset a WiMAX device\n\n Provides wimax_reset() for the kernel to reset a wimax device as\n needed and exports it over generic netlink to user space.\n\nThis API is clearly limited, as it still provides no way to do the\nbasic scan, connect and disconnect in a hardware independent way. The\nWiMAX case is more complex than WiFi due to the way networks are\ndiscovered and provisioned.\n\nThe next developments are to add the basic operations so they can be\nofferent by different drivers. However, we\u0027d like to get more vendors\nto jump in and provide feedback of how the user/kernel API/abstraction\nlayer should be.\n\nThe user space code for the i2400m, as of now, uses the messaging\nchannel, but that will change as the API evolves.\n\nSigned-off-by: Inaky Perez-Gonzalez \u003cinaky@linux.intel.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@suse.de\u003e\n\n" } ] }