/linux/fs/bcachefs/ |
H A D | io_read.c | 166 bch2_data_update_read_done(&op->write, rbio->pick.crc); in promote_start() 173 struct extent_ptr_decoded *pick, in __promote_alloc() argument 281 struct extent_ptr_decoded *pick, in promote_alloc() argument 299 ? max(pick->crc.compressed_size, pick->crc.live_size) in promote_alloc() 315 k, pos, pick, opts, sectors, rbio, failed); in promote_alloc() 441 rbio->pick.ptr, in bch2_read_retry_nodecode() 443 rbio->pick.crc.offset)) { in bch2_read_retry_nodecode() 484 bch2_mark_io_failure(&failed, &rbio->pick); in bch2_rbio_retry() 528 struct bch_dev *ca = rbio->have_ioref ? bch2_dev_have_ref(c, rbio->pick.ptr.dev) : NULL; in bch2_read_io_err() 549 u64 data_offset = rbio->data_pos.offset - rbio->pick.crc.offset; in __bch2_rbio_narrow_crcs() [all …]
|
H A D | btree_io.c | 1316 struct bch_dev *ca = rb->have_ioref ? bch2_dev_have_ref(c, rb->pick.ptr.dev) : NULL; in btree_node_read_work() 1329 ca = bch2_dev_get_ioref(c, rb->pick.ptr.dev, READ); in btree_node_read_work() 1332 bio->bi_iter.bi_sector = rb->pick.ptr.offset; in btree_node_read_work() 1351 bch2_mark_io_failure(&failed, &rb->pick); in btree_node_read_work() 1355 &failed, &rb->pick) > 0; in btree_node_read_work() 1405 struct bch_dev *ca = bch2_dev_have_ref(c, rb->pick.ptr.dev); in btree_node_read_endio() 1602 struct bch_dev *ca = bch2_dev_have_ref(c, rb->pick.ptr.dev); in btree_node_read_all_replicas_endio() 1620 struct extent_ptr_decoded pick; in btree_node_read_all_replicas() local 1643 bkey_for_each_ptr_decode(k.k, ptrs, pick, entry) { in btree_node_read_all_replicas() 1644 struct bch_dev *ca = bch2_dev_get_ioref(c, pick.ptr.dev, READ); in btree_node_read_all_replicas() [all …]
|
H A D | debug.c | 35 struct extent_ptr_decoded pick) in bch2_btree_verify_replica() argument 44 struct bch_dev *ca = bch2_dev_get_ioref(c, pick.ptr.dev, READ); in bch2_btree_verify_replica() 53 bio->bi_iter.bi_sector = pick.ptr.offset; in bch2_btree_verify_replica() 187 struct extent_ptr_decoded pick; in bch2_btree_node_ondisk_to_text() local 193 if (bch2_bkey_pick_read_device(c, bkey_i_to_s_c(&b->key), NULL, &pick) <= 0) { in bch2_btree_node_ondisk_to_text() 198 ca = bch2_dev_get_ioref(c, pick.ptr.dev, READ); in bch2_btree_node_ondisk_to_text() 215 bio->bi_iter.bi_sector = pick.ptr.offset; in bch2_btree_node_ondisk_to_text()
|
H A D | io_read.h | 52 struct extent_ptr_decoded pick; member
|
H A D | btree_io.h | 44 struct extent_ptr_decoded pick; member
|
/linux/Documentation/arch/arm/google/ |
H A D | chromebook-boot-flow.rst | 10 is up to depthcharge_ to pick the right device tree from the `FIT Image`_ and 13 The scheme that depthcharge_ uses to pick the device tree takes into account 47 Then depthcharge_ will pick the first device tree even though 65 revision and try to run old software on it then we'll at pick the
|
/linux/Documentation/process/ |
H A D | backporting.rst | 31 in which case you just cherry-pick it directly using 32 ``git cherry-pick``. However, if the patch comes from an email, as it 42 where the patch applies cleanly and *then* cherry-pick it over to your 47 can apply it to the most recent mainline kernel and then cherry-pick it 57 A good reason to prefer ``git cherry-pick`` over ``git am`` is that git 67 article will assume that you are doing a plain ``git cherry-pick``. 72 Once you have the patch in git, you can go ahead and cherry-pick it into 73 your source tree. Don't forget to cherry-pick with ``-x`` if you want a 89 Uh-oh; the cherry-pick failed with a vaguely threatening message:: 104 If your attempted cherry-pick fails with a conflict, git automatically [all …]
|
H A D | stable-kernel-rules.rst | 47 2. Ask the stable team to pick up a patch already mainlined. 95 git cherry-pick a1f84a3 96 git cherry-pick 1b9508f 97 git cherry-pick fd21073 98 git cherry-pick <this commit> 117 git cherry-pick <this commit> 124 * Delay pick up of patches::
|
/linux/Documentation/driver-api/acpi/ |
H A D | linuxized-acpica.rst | 239 1. Cherry-pick an ACPICA commit 242 you want to cherry pick must be committed into the local repository. 244 Then the gen-patch.sh command can help to cherry-pick an ACPICA commit 252 cherry pick. It can be omitted if the commit is "HEAD". 254 2. Cherry-pick recent ACPICA commits
|
/linux/Documentation/translations/it_IT/process/ |
H A D | stable-kernel-rules.rst | 108 git cherry-pick a1f84a3 109 git cherry-pick 1b9508f 110 git cherry-pick fd21073 111 git cherry-pick <this commit> 128 git cherry-pick <this commit>
|
/linux/Documentation/devicetree/bindings/regulator/ |
H A D | ti-abb-regulator.txt | 47 - "efuse-address" - Contains efuse base address used to pick up ABB info. 56 from efuse-address to pick up ABB characteristics. Set to 0 if
|
/linux/Documentation/maintainer/ |
H A D | rebasing-and-merging.rst | 71 - If you must reparent a repository, do not pick some random kernel commit 75 series must move to a new base, pick a stable point (such as one of 210 the development cycle in order to pick up changes and fixes done elsewhere 211 in the tree. As always, such a merge should pick a well-known release
|
/linux/Documentation/usb/ |
H A D | dwc3.rst | 9 Please pick something while reading :)
|
/linux/fs/xfs/libxfs/ |
H A D | xfs_dir2_sf.c | 374 int pick; /* which algorithm to use */ in xfs_dir2_sf_addname() local 408 (pick = in xfs_dir2_sf_addname() 431 if (pick == 1) in xfs_dir2_sf_addname() 438 ASSERT(pick == 2); in xfs_dir2_sf_addname()
|
/linux/Documentation/arch/arm/ |
H A D | vlocks.rst | 73 atomicity is used to pick the winner. This avoids the need for a static 90 to pick a unique winner, but it does not matter which CPU actually
|
/linux/tools/include/uapi/ |
H A D | README | 66 The tooling policy is to always pick up the kernel side headers as-is,
|
/linux/lib/ |
H A D | fortify_kunit.c | 96 static volatile int pick; variable 99 static noinline size_t want_minus_one(int pick) in want_minus_one() argument 103 switch (pick) { in want_minus_one() 119 KUNIT_EXPECT_EQ(test, want_minus_one(pick), SIZE_MAX); in fortify_test_control_flow_split()
|
/linux/Documentation/i2c/ |
H A D | i2c-address-translators.rst | 87 2. When the attach callback is called pick an appropriate alias,
|
/linux/Documentation/admin-guide/mm/ |
H A D | swap_numa.rst | 71 or the system will pick one starting from -1 then downwards. The priority
|
/linux/Documentation/driver-api/media/ |
H A D | v4l2-dev.rst | 208 to let the v4l2 framework pick the first free number. But sometimes users 220 and the v4l2 framework will try to pick the first free number that is equal 221 or higher to what you passed. If that fails, then it will just pick the
|
/linux/samples/bpf/ |
H A D | README.rst | 51 level directory, that the make system will automatically pick up first.
|
/linux/Documentation/leds/ |
H A D | well-known-leds.txt | 29 though drivers may pick a default value.
|
/linux/drivers/firmware/ |
H A D | Kconfig | 201 drivers like efifb, vesafb and uvesafb can pick it up. 206 not be able to pick up generic system framebuffers if this option
|
/linux/Documentation/hwmon/ |
H A D | w83793.rst | 86 will always pick the safest (max) PWM value for each fan.
|
/linux/Documentation/arch/x86/ |
H A D | entry_64.rst | 67 The cheap way is to pick this info off the entry frame on the kernel
|