)]}' { "log": [ { "commit": "b91d0e364077fad401454699143ad6a78902c20a", "tree": "9cff43a299e31011b67eea1e58673a11ad284d1d", "parents": [ "f41f3f373dd72344c65d801d6381fe83ef3a2c54" ], "author": { "name": "Johannes Berg", "email": "johannes@sipsolutions.net", "time": "Mon Jun 08 08:14:28 2009 +0200" }, "committer": { "name": "John W. Linville", "email": "linville@tuxdriver.com", "time": "Wed Jun 10 13:27:54 2009 -0400" }, "message": "rfkill: remove input Kconfig\n\nNow that we added the ioctl, there\u0027s no need to ask\nthe user to configure this. We will keep it enabled\nfor now, and eventually swap the default to n. Also\nlet embedded users select it only if they need it.\n\nSigned-off-by: Johannes Berg \u003cjohannes@sipsolutions.net\u003e\nSigned-off-by: John W. Linville \u003clinville@tuxdriver.com\u003e\n" }, { "commit": "c64fb01627e24725d1f9d535e4426475a4415753", "tree": "24b7e5caef5b1ddeaf479c98d56b2c38e25fca57", "parents": [ "19d337dff95cbf76edd3ad95c0cee2732c3e1ec5" ], "author": { "name": "Johannes Berg", "email": "johannes@sipsolutions.net", "time": "Tue Jun 02 13:01:38 2009 +0200" }, "committer": { "name": "John W. Linville", "email": "linville@tuxdriver.com", "time": "Wed Jun 03 14:06:14 2009 -0400" }, "message": "rfkill: create useful userspace interface\n\nThe new code added by this patch will make rfkill create\na misc character device /dev/rfkill that userspace can use\nto control rfkill soft blocks and get status of devices as\nwell as events when the status changes.\n\nUsing it is very simple -- when you open it you can read\na number of times to get the initial state, and every\nfurther read blocks (you can poll) on getting the next\nevent from the kernel. The same structure you read is\nalso used when writing to it to change the soft block of\na given device, all devices of a given type, or all\ndevices.\n\nThis also makes CONFIG_RFKILL_INPUT selectable again in\norder to be able to test without it present since its\nfunctionality can now be replaced by userspace entirely\nand distros and users may not want the input part of\nrfkill interfering with their userspace code. We will\nalso write a userspace daemon to handle all that and\nconsequently add the input code to the feature removal\nschedule.\n\nIn order to have rfkilld support both kernels with and\nwithout CONFIG_RFKILL_INPUT (or new kernels after its\neventual removal) we also add an ioctl (that only exists\nif rfkill-input is present) to disable rfkill-input.\nIt is not very efficient, but at least gives the correct\nbehaviour in all cases.\n\nSigned-off-by: Johannes Berg \u003cjohannes@sipsolutions.net\u003e\nAcked-by: Marcel Holtmann \u003cmarcel@holtmann.org\u003e\nSigned-off-by: John W. Linville \u003clinville@tuxdriver.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": "135900c182c321a4888ec496b014e6707272faca", "tree": "d17a3e12bf2e047c7a627f61e623e40dfbad87bf", "parents": [ "937a049dd903bd810d858d0303cf86af9eb08b6f" ], "author": { "name": "Michael Buesch", "email": "mb@bu3sch.de", "time": "Thu Sep 27 21:33:12 2007 +0200" }, "committer": { "name": "David S. Miller", "email": "davem@sunset.davemloft.net", "time": "Wed Oct 10 16:54:10 2007 -0700" }, "message": "[RFKILL]: Add support for an rfkill LED.\n\nThis adds a LED trigger.\n\nSigned-off-by: Michael Buesch \u003cmb@bu3sch.de\u003e\nAcked-by: Ivo van Doorn \u003cIvDoorn@gmail.com\u003e\nSigned-off-by: John W. Linville \u003clinville@tuxdriver.com\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\n" }, { "commit": "234a0ca6f1d67ba4c3c3fc8378bbd98d722468e1", "tree": "a744629408146be683dfbef5c18f1f8bb433f3b7", "parents": [ "077130c0cf7d5ba1992f5b51b96136d7b1c8aad5" ], "author": { "name": "Ivo van Doorn", "email": "IvDoorn@gmail.com", "time": "Thu Sep 13 09:20:42 2007 +0200" }, "committer": { "name": "David S. Miller", "email": "davem@sunset.davemloft.net", "time": "Wed Oct 10 16:49:23 2007 -0700" }, "message": "[RFKILL]: Remove IRDA\n\nAs Dmitry pointed out earlier, rfkill-input.c\ndoesn\u0027t support irda because there are no users\nand we shouldn\u0027t add unrequired KEY_ defines.\n\nHowever, RFKILL_TYPE_IRDA was defined in the\nrfkill.h header file and would confuse people\nabout whether it is implemented or not.\n\nThis patch removes IRDA support completely,\nso it can be added whenever a driver wants the\nfeature.\n\nSigned-off-by: Ivo van Doorn \u003cIvDoorn@gmail.com\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\n" }, { "commit": "cf4328cd949c2086091c62c5685f1580fe9b55e4", "tree": "bd9d96f1c99910076b6f5f34cd5cd2da30405ef1", "parents": [ "2396a22e0989df6038996506bfbf7a57f116c299" ], "author": { "name": "Ivo van Doorn", "email": "IvDoorn@gmail.com", "time": "Mon May 07 00:34:20 2007 -0700" }, "committer": { "name": "David S. Miller", "email": "davem@davemloft.net", "time": "Mon May 07 00:34:20 2007 -0700" }, "message": "[NET]: rfkill: add support for input key to control wireless radio\n\nThe RF kill patch that provides infrastructure for implementing\nswitches controlling radio states on various network and other cards.\n\n[dtor@insightbb.com: address review comments]\n[akpm@linux-foundation.org: cleanups, build fixes]\n\nSigned-off-by: Ivo van Doorn \u003cIvDoorn@gmail.com\u003e\nSigned-off-by: Andrew Morton \u003cakpm@linux-foundation.org\u003e\nSigned-off-by: Dmitry Torokhov \u003cdtor@mail.ru\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\n" } ] }