Home
last modified time | relevance | path

Searched refs:our (Results 1 – 25 of 223) sorted by relevance

123456789

/linux-6.15/Documentation/process/
H A Dkernel-enforcement-statement.rst6 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 Dindex.rst14 to learn about how our community works. Reading these documents will make
76 documents below provide general advice about debugging and describe our
H A Dcode-of-conduct.rst10 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-6.15/drivers/net/ethernet/chelsio/
H A DKconfig31 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-6.15/Documentation/gpu/amdgpu/display/
H A Dindex.rst8 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 Ddcn-overview.rst7 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-6.15/drivers/crypto/chelsio/
H A DKconfig14 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-6.15/drivers/scsi/csiostor/
H A DKconfig11 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-6.15/drivers/infiniband/hw/cxgb4/
H A DKconfig12 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-6.15/Documentation/networking/device_drivers/ethernet/wangxun/
H A Dngbe.rst12 If you have problems with the software or hardware, please contact our
13 customer support team via email at [email protected] or check our website
/linux-6.15/tools/testing/selftests/net/packetdrill/
H A Dtcp_close_close-remote-fin-then-close.pkt3 // Since the remote side (client) closes first, we test our LAST_ACK code path.
30 // Client ACKs our FIN.
H A Dtcp_blocking_blocking-write.pkt20 // Kernel doubles our value -> sk->sk_sndbuf is set to 42000
H A Dtcp_ts_recent_invalid_ack.pkt20 // bad packet with high tsval (its ACK sequence is above our sndnxt)
/linux-6.15/arch/parisc/math-emu/
H A DREADME5 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-6.15/arch/alpha/lib/
H A Dstrrchr.S22 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-6.15/Documentation/driver-api/usb/
H A Dwriting_usb_driver.rst167 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-6.15/drivers/gpu/drm/nouveau/nvkm/subdev/pmu/fuc/
H A Didle.fuc52 // set our "no interrupt has occurred during our execution" flag
/linux-6.15/Documentation/devicetree/bindings/i2c/
H A Di2c-arb-gpio-challenge.yaml58 our-claim-gpios:
95 - our-claim-gpios
109 our-claim-gpios = <&gpf0 3 GPIO_ACTIVE_LOW>;
H A Di2c-gpio.yaml59 description: this means that something outside of our control has put
66 description: this means that something outside of our control has put the
/linux-6.15/arch/arm/mach-shmobile/
H A Dheadsmp-scu.S27 bic r2, r2, r3 @ Clear bits of our CPU (Run Mode)
/linux-6.15/drivers/scsi/aic7xxx/
H A Daic79xx.seq130 * long as one of our data FIFOs is active.
322 /* Increment our position in the QINFIFO. */
502 * until we return to our idle loop), use a
624 * the point of selection until our idle
625 * loop determines that neither of our FIFOs
665 * Continue to our normal state machine.
677 * the point of re-selection until our idle
678 * loop determines that neither of our FIFOs
874 * Command retry. Free our current FIFO and
1426 * data byte on the bus until we send our ACK.
[all …]
/linux-6.15/Documentation/filesystems/bcachefs/
H A DCodingStyle.rst6 Good development is like gardening, and codebases are our gardens. Tend to them
23 Assertions are one of our most important tools for writing reliable code. If in
55 can still incorporate that kind of thinking into our code and document the
171 The most important tools (besides the compiler and our text editor) are the
174 errors in our thinking by running our code and seeing what happens. If your
/linux-6.15/Documentation/driver-api/iio/
H A Dtriggers.rst39 trigger with our device by writing the trigger's name in the
54 /* first, allocate memory for our trigger */
/linux-6.15/Documentation/ABI/testing/
H A Dsysfs-driver-tegra-fuse1 What: /sys/devices/*/<our-device>/fuse
H A Dsysfs-driver-jz4780-efuse1 What: /sys/devices/*/<our-device>/nvmem

123456789