Searched refs:appending (Results 1 – 18 of 18) sorted by relevance
| /linux/fs/ubifs/ |
| H A D | file.c | 212 int err, appending = !!(pos + len > inode->i_size); in write_begin_slow() local 226 if (appending) in write_begin_slow() 276 if (appending) { in write_begin_slow() 312 struct ubifs_inode *ui, int appending) in allocate_budget() argument 317 if (!appending) in allocate_budget() 360 if (appending) { in allocate_budget() 416 int err, appending = !!(pos + len > inode->i_size); in ubifs_write_begin() local 456 err = allocate_budget(c, folio, ui, appending); in ubifs_write_begin() 472 if (appending) { in ubifs_write_begin() 503 struct ubifs_inode *ui, int appending) in cancel_budget() argument [all …]
|
| H A D | tnc.c | 2122 int i, keep, move, appending = 0; in tnc_insert() local 2169 appending = 1; in tnc_insert() 2172 } else if (appending && n != c->fanout) { in tnc_insert() 2174 appending = 0; in tnc_insert() 2192 if (appending) { in tnc_insert()
|
| /linux/Documentation/staging/ |
| H A D | crc32.rst | 31 is sent last. And when appending a CRC word to a message, you should 178 Normally, appending zero bits to a message which is already a multiple 182 appending it. This makes the remainder of the message+crc come out not
|
| /linux/Documentation/block/ |
| H A D | data-integrity.rst | 18 support for appending integrity metadata to an I/O. The integrity 45 The SCSI Data Integrity Field works by appending 8 bytes of protection
|
| /linux/arch/arm/mach-omap1/ |
| H A D | ams-delta-fiq-handler.S | 188 @ Try appending the keycode to the circular buffer
|
| /linux/Documentation/process/debugging/ |
| H A D | gdb-kernel-debugging.rst | 48 - at VM startup time by appending "-s" to the QEMU command line
|
| /linux/Documentation/admin-guide/mm/ |
| H A D | numaperf.rst | 71 node sysfs hierarchy by appending the attributes directory under the
|
| /linux/net/netfilter/ipvs/ |
| H A D | Kconfig | 74 or by appending ip_vs.conn_tab_bits=? to the kernel command line if
|
| /linux/Documentation/kbuild/ |
| H A D | gendwarfksyms.rst | 327 Space is typically reserved for later use by appending integer types, or
|
| /linux/tools/perf/Documentation/ |
| H A D | perf-list.txt | 58 Events can optionally have a modifier by appending a colon and one or
|
| H A D | perf-stat.txt | 523 appending '_group' to it and this will increase accuracy compared to
|
| /linux/Documentation/driver-api/ |
| H A D | device_link.rst | 225 or OpenFirmware device tree top-down and appending devices to the lists
|
| H A D | xillybus.rst | 272 buffer is full, the FPGA informs the host about that (appending a
|
| /linux/Documentation/driver-api/usb/ |
| H A D | dwc3.rst | 95 fully capable of appending a chained TRB for the remaining length and
|
| /linux/Documentation/security/ |
| H A D | ipe.rst | 317 reads (imagine appending to a log file).
|
| /linux/drivers/md/ |
| H A D | Kconfig | 97 partitions by simply appending one to the other.
|
| /linux/Documentation/trace/ |
| H A D | ftrace.rst | 3327 in a different module is accomplished by appending (>>) to the
|
| /linux/Documentation/admin-guide/ |
| H A D | cgroup-v2.rst | 3265 construct the path by appending the name of the knob to the path, open
|