| /linux/Documentation/netlabel/ |
| H A D | introduction.rst | 24 engine will handle those tasks as well. Other kernel subsystems should
37 formatting of these NetLabel messages as well as the Generic NETLINK family
39 header files as well as in 'include/net/netlabel.h'.
51 'include/net/netlabel.h' header file as well as the 'lsm_interface.txt' file
|
| H A D | lsm_interface.rst | 35 on outgoing packets as well as read the labels on incoming packets. Functions
36 exist to operate both on sockets as well as the sk_buffs directly. These high
53 bypassed as well which should result in a significant reduction in overhead.
|
| /linux/Documentation/maintainer/ |
| H A D | rebasing-and-merging.rst | 91 well-known starting point, and they are well tested, the potential for
140 Such merges need to be carefully thought about and well justified, or
155 a well-managed branch.
159 merge to a well-known stable point, rather than to some random commit.
198 merging of your tree as well. Preferable alternatives include agreeing
211 in the tree. As always, such a merge should pick a well-known release
|
| /linux/include/drm/ |
| H A D | drm_audio_component.h | 22 * @get_power: get the POWER_DOMAIN_AUDIO power well
24 * Request the power well to be turned on.
31 * @put_power: put the POWER_DOMAIN_AUDIO power well
33 * Allow the power well to be turned off.
|
| /linux/Documentation/admin-guide/cifs/ |
| H A D | introduction.rst | 5 This is the client VFS module for the SMB3 NAS protocol as well
16 well as by Samba (which provides excellent CIFS/SMB2/SMB3 server
18 Apple systems also support SMB3 well, as do most Network Attached
|
| /linux/drivers/input/tablet/ |
| H A D | Kconfig | 23 (CONFIG_INPUT_EVDEV) as well.
36 support" (CONFIG_INPUT_EVDEV) as well.
60 (CONFIG_INPUT_EVDEV) as well.
|
| /linux/Documentation/admin-guide/media/ |
| H A D | cafe_ccic.rst | 17 well, but that is a debugging aid which will be removed shortly). VGA and
34 loading via sysfs as well:
49 systems, however, it will work well with only two.
|
| /linux/Documentation/i2c/busses/ |
| H A D | i2c-sis96x.rst | 47 chipsets as well: 635, and 635T. If anyone owns a board with those chips
48 AND is willing to risk crashing & burning an otherwise well-behaved kernel
51 reports and/or success stories as well.
|
| /linux/Documentation/hwmon/ |
| H A D | aquacomputer_d5next.rst | 31 virtual temperature sensors, as well as two flow sensors. The fans expose their
36 and current, as well as coolant temperature and eight virtual temp sensors. Also
49 as well as eight PWM controllable fans, along with their speed (in RPM), power, voltage
69 and fan IC. It also exposes pump and fan speeds (in RPM), voltages, as well as pump
|
| /linux/tools/perf/pmu-events/arch/x86/broadwellde/ |
| H A D | uncore-interconnect.json | 285 "PublicDescription": "Counts the number of cycles when the BL Ingress is full. This queue is where the IRP receives data from R2PCIe (the ring). It is used for data returns from read requests as well as outbound MMIO writes.",
294 "PublicDescription": "Counts the number of allocations into the BL Ingress. This queue is where the IRP receives data from R2PCIe (the ring). It is used for data returns from read requests as well as outbound MMIO writes.",
303 "PublicDescription": "Accumulates the occupancy of the BL Ingress in each cycles. This queue is where the IRP receives data from R2PCIe (the ring). It is used for data returns from read requests as well as outbound MMIO writes.",
312 "PublicDescription": "Counts the number of cycles when the BL Ingress is full. This queue is where the IRP receives data from R2PCIe (the ring). It is used for data returns from read requests as well as outbound MMIO writes.",
321 "PublicDescription": "Counts the number of allocations into the BL Ingress. This queue is where the IRP receives data from R2PCIe (the ring). It is used for data returns from read requests as well as outbound MMIO writes.",
330 "PublicDescription": "Accumulates the occupancy of the BL Ingress in each cycles. This queue is where the IRP receives data from R2PCIe (the ring). It is used for data returns from read requests as well as outbound MMIO writes.",
339 "PublicDescription": "Counts the number of cycles when the BL Ingress is full. This queue is where the IRP receives data from R2PCIe (the ring). It is used for data returns from read requests as well as outbound MMIO writes.",
348 "PublicDescription": "Counts the number of allocations into the BL Ingress. This queue is where the IRP receives data from R2PCIe (the ring). It is used for data returns from read requests as well as outbound MMIO writes.",
357 "PublicDescription": "Accumulates the occupancy of the BL Ingress in each cycles. This queue is where the IRP receives data from R2PCIe (the ring). It is used for data returns from read requests as well as outbound MMIO writes.",
|
| /linux/drivers/staging/media/ipu3/ |
| H A D | TODO | 5 as well as formats and the binary used to a request. Remove the
12 documentation. This may require driver changes as well.
|
| /linux/Documentation/bpf/ |
| H A D | bpf_devel_QA.rst | 22 A: Since all BPF kernel development as well as bpftool and iproute2 BPF
38 the actual commit authors in Cc as well for the report. They can
70 such, your patch set will automatically (be attempted to) be rebased as well.
82 lists and maintainers from there as well, so they are able to review
294 bpftool should be extended as well to support dumping them.
300 iproute2's BPF loader as well from user space side. This is not only
305 Q: Do you accept patches as well for iproute2's BPF loader?
312 please keep them in Cc as well, so they can be reviewed.
364 that would require BPF JIT and/or LLVM integration as well?
421 Q: The BPF patch I am about to submit needs to go to stable as well
[all …]
|
| /linux/Documentation/arch/x86/ |
| H A D | kernel-stacks.rst | 74 Using a separate stack allows the kernel to recover from it well enough
140 or not - but in most cases we'll get the call chain right as well. The
142 information from that as well.
147 we still print out the real call chain as well - just with more question
|
| /linux/Documentation/scsi/ |
| H A D | BusLogic.rst | 39 well and have very low command latency. BusLogic has recently provided me with
45 Adapters as well.
56 well as the most recent release of this driver and the latest firmware for the
73 adapters that have been well tested with Linux even before being brought to
107 reported for each target device, as well as the status of Tagged Queuing.
154 tagged queuing for each target device as well as individual selection of the
174 associated with the command being reset, as well as suppressing error
279 list. The retail kit includes the bare board and manual as well as cabling and
406 well as PCI Multimaster Host Adapters that have their ISA Compatible I/O
442 Target Devices that support Tagged Queuing, as well as the maximum Queue
|
| /linux/Documentation/process/ |
| H A D | 2.Process.rst | 168 well.
323 TODO file should be present in the directory as well. The TODO file lists
325 proper, as well as a list of people that should be Cc'd for any patches to
343 directions. The whole thing would not work anywhere near as well as it
345 are well beyond the scope of this document, but there is space for a few
350 systems being developed in the free software community. It is well tuned
351 for kernel development, in that it performs quite well when dealing with
462 Companies often look to hire well-known developers to get a development
468 the kernel and the company both, and who can help to train others as well.
|
| /linux/drivers/firmware/ |
| H A D | ti_sci.c | 395 * return corresponding error, else if all goes well,
509 * Return: 0 if all went well, else returns appropriate error value.
946 * Return: 0 if all went well, else returns appropriate error value.
1011 * Return: 0 if all went well, else returns appropriate error value.
1087 * Return: 0 if all went well, else returns appropriate error value.
1113 * Return: 0 if all went well, else returns appropriate error value.
1133 * Return: 0 if all went well, else returns appropriate error value.
1152 * Return: 0 if all went well, else returns appropriate error value.
1181 * Return: 0 if all went well, else returns appropriate error value.
1214 * Return: 0 if all went well, else returns appropriate error value.
[all …]
|
| /linux/Documentation/RCU/ |
| H A D | NMI-RCU.rst | 9 handlers, as well as dynamic irq handlers. This document describes
82 dummy_nmi_handler(). However, there may well be an NMI handler
109 The caller to set_nmi_callback() might well have
|
| /linux/Documentation/admin-guide/laptops/ |
| H A D | toshiba_haps.rst | 28 userspace tools or daemons act accordingly, as well as providing a sysfs
48 any "protection" as well as failing during the evaluation of the _STA method
77 level, as well as set the desired protection level, the
|
| /linux/net/appletalk/ |
| H A D | Kconfig | 13 well as access AppleTalk printers. Check out
24 information as well.
|
| /linux/Documentation/devicetree/bindings/net/ |
| H A D | brcm,bcm6368-mdio-mux.yaml | 13 This MDIO bus multiplexer defines buses that could be internal as well as
15 properties as well to generate desired MDIO transaction on appropriate bus.
|
| /linux/Documentation/sound/cards/ |
| H A D | pcmtest.rst | 7 testing/fuzzing of the userspace ALSA applications, as well as for testing/fuzzing of
26 RESET ioctl, and the selftest covers this PCM API functionality as well.
49 for each channel, as well as entries which contain the pattern buffer length.
|
| /linux/net/ax25/ |
| H A D | Kconfig | 40 radio as well as information about how to configure an AX.25 port is
88 users as well as information about how to configure an AX.25 port is
107 users as well as information about how to configure an AX.25 port is
|
| /linux/arch/arc/include/asm/ |
| H A D | barrier.h | 19 * - DMB guarantees SMP as well as local barrier semantics
34 * heavy weight as it flushes the pipeline as well.
|
| /linux/Documentation/driver-api/ |
| H A D | isa.rst | 23 that all device creation has been made internal as well.
56 well.
101 well.
|
| /linux/Documentation/filesystems/bcachefs/ |
| H A D | SubmittingPatches.rst | 31 Focus on writing code that reads well and is organized well; code should be
91 on IRC as well [4]_; many people appreciate the more conversational approach
|