Linux kernel documentation tree maintained by Jonathan Corbet http://mirrors.hust.edu.cn/git/lwn.git/atom?h=v5.14 2015-11-17T17:49:19+00:00 2015-11-17T17:49:19+00:00 Kalle Valo kvalo@codeaurora.org 2015-11-17T17:49:19+00:00 urn:sha1:d4a173040a1023e9e0443ea572f4685df406cde9 Part of reorganising wireless drivers directory and Kconfig. Signed-off-by: Kalle Valo <kvalo@codeaurora.org> 2015-06-10T14:05:36+00:00 Johannes Berg johannes.berg@intel.com 2015-06-02T19:39:54+00:00 urn:sha1:30686bf7f5b3c30831761e188a6e3cb33580fa48 As we're running out of hardware capability flags pretty quickly, convert them to use the regular test_bit() style unsigned long bitmaps. This introduces a number of helper functions/macros to set and to test the bits, along with new debugfs code. The occurrences of an explicit __clear_bit() are intentional, the drivers were never supposed to change their supported bits on the fly. We should investigate changing this to be a per-frame flag. Signed-off-by: Johannes Berg <johannes.berg@intel.com> 2015-05-26T10:47:36+00:00 Okash Khawaja okash.khawaja@gmail.com 2015-05-11T11:58:31+00:00 urn:sha1:fe0a483ecf4458e94ebe58d7fedc6d56e21eed56 The PCI cache line size value was being compared against decimal values prefixed with 0x. Fixed the literals to use the correct hex values. This has not been tested due to lack of hardware. However, the value in `cline` is PCI cache line size, which is the CPU's cache line size. It is less likely for cache line sizes to be 22 or 50, and more likely for them to be 16 or 32. Also, as far as I understand, cache line size is used for things like aligning DMA requests with CPU cache line, which improve performance but wouldn't break anything if the value doesn't match. In this case, we will fall through to the default case which leaves `reg` unchanged. Signed-off-by: Okash Khawaja <okash.khawaja@gmail.com> Signed-off-by: Kalle Valo <kvalo@codeaurora.org> 2015-05-26T10:47:28+00:00 Okash Khawaja okash.khawaja@gmail.com 2015-05-11T11:53:25+00:00 urn:sha1:f5c65f38912e38fc035dd1e515c1442bf62a8dab This patch fixes these checkpatch.pl errors around a single switch-case block: ERROR: switch and case should be at the same indent ERROR: trailing statements should be on next line More specifically, the fix has been applied to the five occurances of the errors listed below. ERROR: switch and case should be at the same indent #1100: FILE: adm8211.c:1100: + switch (cline) { [...] + default: reg |= (0x0 << 14); ERROR: trailing statements should be on next line #1101: FILE: adm8211.c:1101: + case 0x8: reg |= (0x1 << 14); ERROR: trailing statements should be on next line #1103: FILE: adm8211.c:1103: + case 0x16: reg |= (0x2 << 14); ERROR: trailing statements should be on next line #1105: FILE: adm8211.c:1105: + case 0x32: reg |= (0x3 << 14); ERROR: trailing statements should be on next line #1107: FILE: adm8211.c:1107: + default: reg |= (0x0 << 14); Signed-off-by: Okash Khawaja <okash.khawaja@gmail.com> Signed-off-by: Kalle Valo <kvalo@codeaurora.org> 2015-04-24T09:14:13+00:00 Johannes Berg johannes.berg@intel.com 2015-04-22T12:40:58+00:00 urn:sha1:df1404650ccbfeb76a84f301f22316be0d00a864 This support is essentially useless as typically networks are encrypted, frames will be filtered by hardware, and rate scaling will be done with the intended recipient in mind. For real monitoring of the network, the monitor mode support should be used instead. Removing it removes a lot of corner cases. Signed-off-by: Johannes Berg <johannes.berg@intel.com> 2015-01-15T12:44:42+00:00 Julia Lawall Julia.Lawall@lip6.fr 2014-12-29T17:04:41+00:00 urn:sha1:72e121191c0b4bde8cd2cea24c0ebc9d70bf8037 Return a negative error code on failure. A simplified version of the semantic match that finds this problem is as follows: (http://coccinelle.lip6.fr/) // <smpl> @@ identifier ret; expression e1,e2; @@ ( if (\(ret < 0\|ret != 0\)) { ... return ret; } | ret = 0 ) ... when != ret = e1 when != &ret *if(...) { ... when != ret = e2 when forall return ret; } // </smpl> Signed-off-by: Julia Lawall <Julia.Lawall@lip6.fr> Signed-off-by: Kalle Valo <kvalo@codeaurora.org> 2014-08-12T18:15:14+00:00 Benoit Taine benoit.taine@lip6.fr 2014-08-08T13:56:03+00:00 urn:sha1:9baa3c34ac4e27f7e062f266f50cc5dbea26a6c1 We should prefer `struct pci_device_id` over `DEFINE_PCI_DEVICE_TABLE` to meet kernel coding style guidelines. This issue was reported by checkpatch. A simplified version of the semantic patch that makes this change is as follows (http://coccinelle.lip6.fr/): // <smpl> @@ identifier i; declarer name DEFINE_PCI_DEVICE_TABLE; initializer z; @@ - DEFINE_PCI_DEVICE_TABLE(i) + const struct pci_device_id i[] = z; // </smpl> [bhelgaas: add semantic patch] Signed-off-by: Benoit Taine <benoit.taine@lip6.fr> Signed-off-by: Bjorn Helgaas <bhelgaas@google.com> 2014-01-17T19:43:17+00:00 John W. Linville linville@tuxdriver.com 2014-01-17T19:43:17+00:00 urn:sha1:7916a075571f0ccd0830cf3da293188a8b6045e3 2014-01-13T19:40:59+00:00 John W. Linville linville@tuxdriver.com 2014-01-13T19:40:59+00:00 urn:sha1:f13352519ee8c4b22b87fc1a47743d1f53ea193e 2014-01-10T15:59:40+00:00 John W. Linville linville@tuxdriver.com 2014-01-10T15:59:40+00:00 urn:sha1:235f93922878234f3d99a4205ebe3634ee955919 Conflicts: net/ieee802154/6lowpan.c