Searched full:confused (Results 1 – 25 of 232) sorted by relevance
12345678910
187 goto confused; in do_mpage_readpage()232 goto confused; in do_mpage_readpage()253 goto confused; in do_mpage_readpage()257 goto confused; /* hole -> non-hole */ in do_mpage_readpage()261 goto confused; in do_mpage_readpage()290 goto confused; in do_mpage_readpage()311 goto confused; in do_mpage_readpage()330 confused: in do_mpage_readpage()535 goto confused; in __mpage_writepage()542 goto confused; /* hole -> non-hole */ in __mpage_writepage()[all …]
253 goto confused; in ext4_mpage_readpages()314 goto confused; /* hole -> non-hole */ in ext4_mpage_readpages()318 goto confused; in ext4_mpage_readpages()348 goto confused; in ext4_mpage_readpages()393 confused: in ext4_mpage_readpages()
27 This is not to be confused with the support for IBM CAPI
8 guest networking with virtio_net. Not to be confused with virtio_net
34 inputs. Pads should not be confused with physical pins at chip
38 confused with the Ethernet specific 'phy' and 'phy-handle' properties,
33 * fashion that it might be confused with the original M.I.T. software.
73 gets confused)
63 * get confused. in check_irq_resend()
83 printf(" confused\n"); in main()
78 Userspace may get confused by toggling this. If DAWR is force
73 * A 32-bit UML on a 64-bit host gets confused about the VDSO at in os_get_top_address()
10 * Sparse (as at v0.5.0) gets very, very confused by this file.
20 should not be confused with struct device_node objects used by the Device Trees
61 the field order cannot be confused.
79 * so that kbuild is not confused if a .c file in parse_dep_file()
76 * It is not to be confused with conventional non-blocking socket operations.
34 we don't want it confused with a real length. Hence max 254.
59 * Enable port 0x44. The IT8172 spec is confused; it calls in it8172_set_pio_mode()
18 /* Assign 20 so we don't get confused w/ builtin ones */
110 confused with a backlight enable signal.
613 goto confused; in nilfs_do_roll_forward()632 goto confused; in nilfs_do_roll_forward()681 confused: in nilfs_do_roll_forward()
27 * gets confused easily if you unplug one end of the cable then
99 * get very confused if 0 is returned as a legitimate address. in arm_mm_memblock_reserve()
30 * confused user.
