Home
last modified time | relevance | path

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

1234567

/Linux-v4.19/drivers/net/ethernet/chelsio/
DKconfig29 For general information about Chelsio and our products, visit
30 our website at <http://www.chelsio.com>.
32 For customer support, please visit our customer support page at
56 For general information about Chelsio and our products, visit
57 our website at <http://www.chelsio.com>.
59 For customer support, please visit our customer support page at
78 For general information about Chelsio and our products, visit
79 our website at <http://www.chelsio.com>.
81 For customer support, please visit our customer support page at
119 For general information about Chelsio and our products, visit
[all …]
/Linux-v4.19/Documentation/process/
Dkernel-enforcement-statement.rst4 As developers of the Linux kernel, we have a keen interest in how our software
5 is used and how the license for our software is enforced. Compliance with the
7 sustainability of our software and community.
10 contributions made to our community, we share an interest in ensuring that
11 individual enforcement actions are conducted in a manner that benefits our
13 growth of our software ecosystem. In order to deter unhelpful enforcement
14 actions, we agree that it is in the best interests of our development
16 on behalf of ourselves and any successors to our copyright interests:
19 it is in the best interests of our development community to adopt the
20 following provisions of GPL-3.0 as additional permissions under our
[all …]
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-v4.19/drivers/infiniband/hw/cxgb3/
DKconfig9 For general information about Chelsio and our products, visit
10 our website at <http://www.chelsio.com>.
12 For customer support, please visit our customer support page at
/Linux-v4.19/drivers/scsi/csiostor/
DKconfig10 For general information about Chelsio and our products, visit
11 our website at <http://www.chelsio.com>.
13 For customer support, please visit our customer support page at
/Linux-v4.19/drivers/infiniband/hw/cxgb4/
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-v4.19/drivers/crypto/chelsio/
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-v4.19/arch/parisc/math-emu/
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-v4.19/arch/alpha/lib/
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-v4.19/Documentation/i2c/
Dupgrading-clients37 dev_err(dev, "failed to create our state\n");
161 as we are provided with the i2c_client in our example_probe. Instead we
173 And remove the change after our client is attached, as the driver no
190 dev_err(dev, "failed to create our state\n");
241 dev_err(dev, "failed to create our state\n");
/Linux-v4.19/Documentation/devicetree/bindings/i2c/
Di2c-gpio.txt21 - i2c-gpio,sda-open-drain: this means that something outside of our
25 - i2c-gpio,scl-open-drain: this means that something outside of our
Di2c-arb-gpio-challenge.txt44 - our-claim-gpio: The GPIO that we use to claim the bus.
68 our-claim-gpio = <&gpf0 3 1>;
/Linux-v4.19/drivers/gpu/drm/nouveau/nvkm/subdev/pmu/fuc/
Didle.fuc52 // set our "no interrupt has occurred during our execution" flag
/Linux-v4.19/fs/reiserfs/
DREADME97 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
DKconfig19 plugins consistent with our motto ``It takes more than a license to
38 latest benchmarks.:-) Use of this option allows our team to go all
/Linux-v4.19/Documentation/driver-api/usb/
Dwriting_usb_driver.rst164 the program tries to open the device for I/O. We increment our private
165 usage count and save a pointer to our internal structure in the file
170 /* increment our usage count for the module */
173 /* save our object in the file's private structure */
190 /* copy the data from user space into our urb */
193 /* set up our urb */
211 to call our own ``skel_write_bulk_callback`` function. This function is
251 this function we decrement our private usage count and wait for possible
254 /* decrement our usage count for the device */
/Linux-v4.19/arch/arm/mach-shmobile/
Dheadsmp-scu.S36 bic r2, r2, r3 @ Clear bits of our CPU (Run Mode)
/Linux-v4.19/Documentation/fmc/
DFMC-and-SDB.txt2 FMC (FPGA Mezzanine Card) is the standard we use for our I/O devices,
5 In our I/O environments we need to write drivers for each mezzanine
82 changes on our drivers if that happens.
/Linux-v4.19/drivers/scsi/aic7xxx/
Daic79xx.seq130 * 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-v4.19/Documentation/ABI/testing/
Dsysfs-driver-tegra-fuse1 What: /sys/devices/*/<our-device>/fuse
/Linux-v4.19/Documentation/openrisc/
DTODO4 that are due for investigation shortly, i.e. our TODO list:
/Linux-v4.19/Documentation/driver-api/iio/
Dtriggers.rst41 trigger with our device by writing the trigger's name in the
56 /* first, allocate memory for our trigger */
/Linux-v4.19/Documentation/scheduler/
Dsched-domains.txt36 our CPU is on, starting from its base domain and going up the ->parent chain.
44 that group. If it manages to find such a runqueue, it locks both our initial
46 to our runqueue. The exact number of tasks amounts to an imbalance previously
/Linux-v4.19/drivers/gpu/drm/vc4/
DKconfig21 our display setup.
/Linux-v4.19/Documentation/driver-model/
Ddesign-patterns.txt41 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 *

1234567