| /linux/Documentation/process/ |
| H A D | kernel-enforcement-statement.rst | 6 As developers of the Linux kernel, we have a keen interest in how our software
7 is used and how the license for our software is enforced. Compliance with the
9 sustainability of our software and community.
12 contributions made to our community, we share an interest in ensuring that
13 individual enforcement actions are conducted in a manner that benefits our
15 growth of our software ecosystem. In order to deter unhelpful enforcement
16 actions, we agree that it is in the best interests of our development
18 on behalf of ourselves and any successors to our copyright interests:
21 it is in the best interests of our development community to adopt the
22 following provisions of GPL-3.0 as additional permissions under our
[all …]
|
| H A D | index.rst | 14 to learn about how our community works. Reading these documents will make
79 documents below provide general advice about debugging and describe our
|
| H A D | code-of-conduct.rst | 10 contributors and maintainers pledge to making participation in our project and
11 our community a harassment-free experience for everyone, regardless of age, body
|
| /linux/drivers/net/ethernet/chelsio/ |
| H A D | Kconfig | 31 For general information about Chelsio and our products, visit
32 our website at <http://www.chelsio.com>.
34 For customer support, please visit our customer support page at
58 For general information about Chelsio and our products, visit
59 our website at <http://www.chelsio.com>.
61 For customer support, please visit our customer support page at
81 For general information about Chelsio and our products, visit
82 our website at <http://www.chelsio.com>.
84 For customer support, please visit our customer support page at
122 For general information about Chelsio and our products, visit
[all …]
|
| /linux/Documentation/gpu/amdgpu/display/ |
| H A D | index.rst | 8 reason, our Display Core Driver is divided into two pieces:
23 repository has integration tests with our Internal Linux CI farm, and we run a
33 * Ensure that every patch compiles and the entire series pass our set of IGT
35 * Prepare a branch with those patches for our validation team. If there is an
44 seriously, and we never merge anything that fails our validation. Follows an
45 overview of our test set:
70 Notice that someone from our test team will always reply to the cover letter
85 If you want to learn more about our driver details, take a look at the below
|
| H A D | dcn-overview.rst | 7 To equip our readers with the basic knowledge of how AMD Display Core Next
34 * **Display Output (DIO)**: Codify the output to the display connected to our
56 the SDP as the element from our Data Fabric that feeds the display pipe.
61 want to drive an 8k@60Hz with a DSC enabled, our DCN may require 4 DPP and 2
81 that HUBP accesses a surface using a specific format read from memory, and our
186 configuration parameters for multiple scenarios supported by our hardware.
206 based on a large number of parameters and ensure our hardware is able to feed
|
| /linux/drivers/crypto/chelsio/ |
| H A D | Kconfig | 14 For general information about Chelsio and our products, visit
15 our website at <http://www.chelsio.com>.
17 For customer support, please visit our customer support page at
|
| /linux/drivers/scsi/csiostor/ |
| H A D | Kconfig | 11 For general information about Chelsio and our products, visit
12 our website at <http://www.chelsio.com>.
14 For customer support, please visit our customer support page at
|
| /linux/drivers/infiniband/hw/cxgb4/ |
| H A D | Kconfig | 12 For general information about Chelsio and our products, visit
13 our website at <http://www.chelsio.com>.
15 For customer support, please visit our customer support page at
|
| /linux/Documentation/networking/device_drivers/ethernet/wangxun/ |
| H A D | ngbe.rst | 12 If you have problems with the software or hardware, please contact our
13 customer support team via email at nic-support@net-swift.com or check our website
|
| /linux/tools/testing/selftests/net/packetdrill/ |
| H A D | tcp_close_close-remote-fin-then-close.pkt | 3 // Since the remote side (client) closes first, we test our LAST_ACK code path.
30 // Client ACKs our FIN.
|
| /linux/arch/parisc/math-emu/ |
| H A D | README | 5 enough to update our copies with later changes from HP-UX -- it'll
6 make their 'diff' job easier if our code is relatively unmodified.
|
| /linux/arch/alpha/lib/ |
| H A D | strrchr.S | 22 zapnot a1, 1, a1 # e0 : zero extend our test character
24 sll a1, 8, t5 # e0 : replicate our test character
80 addq t6, t0, v0 # .. e1 : add our aligned base ptr to the mix
|
| /linux/Documentation/driver-api/usb/ |
| H A D | writing_usb_driver.rst | 167 the program tries to open the device for I/O. We increment our private
168 usage count and save a pointer to our internal structure in the file
173 /* increment our usage count for the device */
176 /* save our object in the file's private structure */
193 /* copy the data from user space into our urb */
196 /* set up our urb */
216 to call our own ``skel_write_bulk_callback`` function. This function is
256 this function we decrement our private usage count and wait for possible
259 /* decrement our usage count for the device */
|
| /linux/Documentation/core-api/ |
| H A D | list.rst | 78 /* ... Somewhere later in our driver ... */
102 We'll return to our clown car example to illustrate how nodes get added to the
139 In State 1, our list of clowns is still empty::
208 In our clown example, this results in the following somewhat awkward code:
236 Using it would change our code to something like this:
253 This eliminates the need for the list_entry() step, and our loop cursor is now
254 of the type of our payload. The macro is given the member name that corresponds
266 We can extend our previous example to remove one of the entries:
589 In the following example, our starting state, State 0, is the following::
648 them. This is our starting state in "State 0"::
[all …]
|
| /linux/drivers/gpu/drm/nouveau/nvkm/subdev/pmu/fuc/ |
| H A D | idle.fuc | 52 // set our "no interrupt has occurred during our execution" flag
|
| /linux/drivers/scsi/aic7xxx/ |
| H A D | aic79xx.seq | 130 * long as one of our data FIFOs is active.
150 * still be data in our FIFOs draining to the host. Complete
309 * tag set by the host so that our SCB dma engine
322 /* Increment our position in the QINFIFO. */
365 * our batching and round-robin selection scheme
502 * until we return to our idle loop), use a
570 * we are selecting with atn regardless of our packetized
573 * to our negotiation table entry for this selection will
624 * the point of selection until our idle
625 * loop determines that neither of our FIFOs
[all …]
|
| /linux/Documentation/driver-api/iio/ |
| H A D | triggers.rst | 39 trigger with our device by writing the trigger's name in the
54 /* first, allocate memory for our trigger */
|
| /linux/Documentation/scheduler/ |
| H A D | sched-domains.rst | 42 sched domains our CPU is on, starting from its base domain and going up the ->parent
50 that group. If it manages to find such a runqueue, it locks both our initial
52 to our runqueue. The exact number of tasks amounts to an imbalance previously
|
| /linux/arch/arm/mach-shmobile/ |
| H A D | headsmp-scu.S | 27 bic r2, r2, r3 @ Clear bits of our CPU (Run Mode)
|
| /linux/Documentation/dev-tools/kunit/ |
| H A D | run_wrapper.rst | 193 our system.
197 website to a directory in our home directory called toolchains.
216 non-default configuration; then we can write our own``QemuConfig``.
240 be useful for our test environment. Below are the most commonly used
294 our system.
298 website to a specified path in our home directory called toolchains.
|
| /linux/drivers/infiniband/hw/ionic/ |
| H A D | Kconfig | 11 To learn more, visit our website at
|
| /linux/Documentation/driver-api/driver-model/ |
| H A D | design-patterns.rst | 41 called. This is our state container for this instance of the device driver.
114 We can see here that we avoid having global pointers to our struct foo *
|
| /linux/Documentation/scsi/ |
| H A D | aic79xx.rst | 129 - For pre-2.5.X kernels, carefully adjust our segment
131 - Cleanup channel display in our /proc output.
140 to reset our transceivers.
158 - Correct a race condition in our error recovery handler.
530 - Visit our Web site at http://www.adaptec.com/.
546 - Visit our Web site at http://www.adaptec.com/en-US/_common/world_index.
560 - Visit our web site at http://www.adaptec.co.jp/.
|
| /linux/Documentation/ABI/testing/ |
| H A D | sysfs-driver-tegra-fuse | 1 What: /sys/devices/*/<our-device>/fuse
|