Home
last modified time | relevance | path

Searched refs:We (Results 1 – 25 of 474) sorted by relevance

12345678910>>...19

/Linux-v5.10/arch/arm/boot/compressed/
Dhead-sharpsl.S58 bne .SHARPEND @ We have no w100 - Poodle
64 blo .SHARPEND @ We have a PXA250 - Corgi
70 beq .SHARPEND @ We have Shepherd
81 beq .SHARPEND @ We have Spitz
90 beq .SHARPEND @ We have Borzoi
94 b .SHARPEND @ We have Borzoi
/Linux-v5.10/Documentation/vm/
Dovercommit-accounting.rst74 * We account mmap memory mappings
75 * We account mprotect changes in commit
76 * We account mremap changes in size
77 * We account brk
78 * We account munmap
79 * We report the commit status in /proc
/Linux-v5.10/Documentation/admin-guide/LSM/
Dtomoyo.rst57 We believe that inode based security and name based security are complementary
59 multiple LSM modules at the same time. We feel sorry that you have to give up
62 We hope that LSM becomes stackable in future. Meanwhile, you can use non-LSM
64 LSM version of TOMOYO is a subset of non-LSM version of TOMOYO. We are planning
/Linux-v5.10/arch/m68k/fpsp040/
Dbugfix.S222 | We have the opclass 0 situation.
246 | We have the case in which a conflict exists between the cu src or
247 | dest and the dest of the xu. We must clear the instruction in
304 | The frame returned is idle. We must build a busy frame to hold
341 | the code sequence to allow completion. We will jump to
368 | We have the case in which a conflict exists between the cu src or
369 | dest and the dest of the xu. We must clear the instruction in
430 | The frame returned is idle. We must build a busy frame to hold
451 | We have the opclass 2 single source situation.
/Linux-v5.10/arch/arm/include/debug/
Dsa1100.S23 @ We probe for the active serial port here, coherently with
25 @ We assume r1 can be clobbered.
/Linux-v5.10/arch/powerpc/boot/dts/
Dps3.dts21 * We'll get the size of the bootmem block from lv1 after startup,
38 * threads is with an ibm,ppc-interrupt-server#s entry. We'll put one
/Linux-v5.10/Documentation/powerpc/
Dpci_iov_resource_on_powernv.rst55 We call this the RTT.
87 32-bit PCIe accesses. We configure that window at boot from FW and
101 SR-IOV). We basically use the trick of forcing the bridge MMIO windows
126 We have code (fairly new compared to the M32 stuff) that exploits that
129 We configure an M64 window to cover the entire region of address space
131 for the M32, it comes out of a different "reserve"). We configure it
139 - We do the PE# allocation *after* the 64-bit space has been assigned
140 because the addresses we use directly determine the PE#. We then
144 - We cannot "group" segments in HW, so if a device ends up using more
149 SW. We lose a bit of effectiveness of EEH in that case, but that's
[all …]
Dkaslr-booke32.rst24 We will use the first 512M of the low memory to randomize the kernel
25 image. The memory will be split in 64M zones. We will use the lower 8
/Linux-v5.10/Documentation/hwmon/
Dasc7621.rst26 We have enhanced both parts relative to the governing Intel
27 specification. First enhancement is temperature reading resolution. We
38 are active, they are not necessarily reliable or useful externally. We
41 We employ significant filtering that is user tunable as described in the
47 We offer GPIO features on the former VID pins. These are open-drain
51 We offer flexible mapping of temperature readings to thermal zones. Any
74 fan types. We can also support pulse-stretched PWM so that 3-wire fans
/Linux-v5.10/arch/arm/boot/dts/
Drk3288-veyron-sdmmc.dtsi15 * We run sdmmc at max speed; bump up drive strength.
16 * We also have external pulls, so disable the internal ones.
Drk3288-veyron-analog-audio.dtsi81 * HACK: We're going to _pull down_ this _active low_ interrupt
82 * so that it never fires. We don't need this interrupt because
Drk3288-veyron.dtsi245 * vcc18_wl). We'll add those aliases here just to
485 * We run eMMC at max speed; bump up drive strength.
486 * We also have external pulls, so disable the internal ones.
545 * We run sdio0 at max speed; bump up drive strength.
546 * We also have external pulls, so disable the internal ones.
/Linux-v5.10/scripts/gdb/linux/
Dconstants.py.in22 /* We need to stringify expanded macros so that they can be parsed */
32 * We can only switch on configuration items we know are available
/Linux-v5.10/Documentation/i2c/busses/
Di2c-ali1535.rst38 We make sure that the SMB is enabled. We leave the ACPI alone.
/Linux-v5.10/Documentation/block/
Dinline-encryption.rst26 We want to support inline encryption (IE) in the kernel.
28 IE hardware is absent. We also want IE to work with layered devices
44 - We need a way for upper layers like filesystems to specify an encryption
48 - We need a way for device drivers to expose their inline encryption
55 We add a struct bio_crypt_ctx to struct bio that can
64 We introduce a keyslot manager (KSM) that handles the translation from
87 We add a pointer to a ``bi_crypt_context`` and ``keyslot`` to
93 We introduce ``block/blk-crypto-fallback.c``, which allows upper layers to remain
120 ``blk-crypto-fallback``. We will eventually reach a point in blk-mq when a
227 unused, and don't need any refcounting or keyslot programming. We can instead
/Linux-v5.10/tools/bootconfig/samples/
Dbad-override.bconf2 # We can not override pre-defined subkeys with value
Dbad-override2.bconf2 # We can not override pre-defined value with subkey
/Linux-v5.10/Documentation/riscv/
Dpatch-acceptance.rst15 tested code over experimental code. We wish to extend these same
21 We'll only accept patches for new modules or extensions if the
/Linux-v5.10/drivers/staging/rts5208/
DTODO4 - We will use the stack in drivers/mmc to implement
/Linux-v5.10/arch/x86/realmode/rm/
Dtrampoline_64.S42 cli # We should be safe anyway
87 cli # We should be safe anyway
/Linux-v5.10/Documentation/process/
Dkernel-driver-statement.rst10 We, the undersigned Linux kernel developers, consider any closed-source
11 Linux kernel module or driver to be harmful and undesirable. We have
23 We speak only for ourselves, and not for any company we might work for
Dkernel-enforcement-statement.rst41 software. We want companies and individuals to use, modify and distribute
42 this software. We want to work with users in an open and transparent way to
44 enforcement that might limit adoption of our software. We view legal action
/Linux-v5.10/tools/lib/perf/Documentation/
Dlibperf-counting.txt75 We create software events for cpu and task:
121 We create libperf's events for the attributes we defined earlier and add them to the list:
185 We close the whole events list (both events) and remove it together with the threads map:
/Linux-v5.10/Documentation/admin-guide/cgroup-v1/
Dpids.rst82 We can set a limit that is smaller than pids.current, which will stop any new
87 # /bin/echo "We can't even spawn a single process now."
90 # /bin/echo "We can't even spawn a single process now."
/Linux-v5.10/drivers/scsi/aic7xxx/
Daic7xxx.seq70 * Turn off the selection hardware. We need to reset the
104 * We have at least one queued SCB now and we don't have any
163 * We aren't expecting a bus free, so interrupt
186 * We've just been selected. Assert BSY and
240 * initiator. We follow the guidlines from section 6.5
267 * immediately follow the identify. We test for a valid
411 * We carefully toggle SPIOEN to allow us to return the
454 * We've just re-selected an initiator.
570 * We reuse the first 8 bytes of the TARG_SCSIRATE
690 * We assume that the kernel driver may reset us
[all …]

12345678910>>...19