Searched refs:our (Results 1 – 25 of 202) sorted by relevance
123456789
/Linux-v6.6/Documentation/process/ |
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 …]
|
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-v6.6/drivers/net/ethernet/chelsio/ |
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-v6.6/drivers/scsi/csiostor/ |
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-v6.6/drivers/crypto/chelsio/ |
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-v6.6/drivers/infiniband/hw/cxgb4/ |
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-v6.6/Documentation/networking/device_drivers/ethernet/wangxun/ |
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-v6.6/arch/parisc/math-emu/ |
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-v6.6/Documentation/gpu/amdgpu/display/ |
D | index.rst | 8 reason, our Display Core Driver is divided into two pieces: 23 If you want to learn more about our driver details, take a look at the below
|
D | dcn-overview.rst | 5 To equip our readers with the basic knowledge of how AMD Display Core Next 32 * **Display Output (DIO)**: Codify the output to the display connected to our 54 the SDP as the element from our Data Fabric that feeds the display pipe. 59 want to drive an 8k@60Hz with a DSC enabled, our DCN may require 4 DPP and 2 79 that HUBP accesses a surface using a specific format read from memory, and our 184 configuration parameters for multiple scenarios supported by our hardware. 204 based on a large number of parameters and ensure our hardware is able to feed
|
/Linux-v6.6/arch/alpha/lib/ |
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-v6.6/Documentation/driver-api/usb/ |
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-v6.6/Documentation/dev-tools/kunit/ |
D | run_manual.rst | 26 tests can also be built by enabling their config options in our 38 Once we have built our kernel (and/or modules), it is simple to run
|
D | run_wrapper.rst | 191 our system. 195 website to a directory in our home directory called toolchains. 214 non-default configuration; then we can write our own``QemuConfig``. 238 be useful for our test environment. Below are the most commonly used 292 our system. 296 website to a specified path in our home directory called toolchains.
|
/Linux-v6.6/drivers/gpu/drm/nouveau/nvkm/subdev/pmu/fuc/ |
D | idle.fuc | 52 // set our "no interrupt has occurred during our execution" flag
|
/Linux-v6.6/fs/reiserfs/ |
D | README | 97 Anatoly Pinchuk is a former member of our team who worked closely with 110 curious, because he never really understood the value of our project, 120 our group. 131 Chris Mason dived right into our code, and in just a few months produced 136 for our next major release. 154 anymore, and to dramatically increase our staffing. Ecila funded
|
/Linux-v6.6/arch/arm/mach-shmobile/ |
D | headsmp-scu.S | 27 bic r2, r2, r3 @ Clear bits of our CPU (Run Mode)
|
/Linux-v6.6/drivers/scsi/aic7xxx/ |
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-v6.6/Documentation/driver-api/iio/ |
D | triggers.rst | 39 trigger with our device by writing the trigger's name in the 54 /* first, allocate memory for our trigger */
|
/Linux-v6.6/Documentation/ABI/testing/ |
D | sysfs-driver-jz4780-efuse | 1 What: /sys/devices/*/<our-device>/nvmem
|
D | sysfs-driver-tegra-fuse | 1 What: /sys/devices/*/<our-device>/fuse
|
/Linux-v6.6/Documentation/scheduler/ |
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-v6.6/Documentation/arch/openrisc/ |
D | todo.rst | 8 that are due for investigation shortly, i.e. our TODO list:
|
/Linux-v6.6/Documentation/driver-api/driver-model/ |
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-v6.6/Documentation/devicetree/bindings/interrupt-controller/ |
D | csky,mpintc.txt | 9 0-15 : software irq, and we use 15 as our IPI_IRQ.
|
123456789