| /linux/net/rxrpc/ |
| H A D | conn_client.c | 86 bundle->upgrade = test_bit(RXRPC_CALL_UPGRADE, &call->flags); in rxrpc_alloc_bundle()
182 conn->upgrade = bundle->upgrade; in rxrpc_alloc_client_connection()
256 bool upgrade = test_bit(RXRPC_CALL_UPGRADE, &call->flags); in rxrpc_look_up_bundle() local
260 upgrade); in rxrpc_look_up_bundle()
278 cmp(bundle->upgrade, upgrade)); in rxrpc_look_up_bundle()
307 cmp(bundle->upgrade, upgrade)); in rxrpc_look_up_bundle()
389 if (!usable && bundle->upgrade) in rxrpc_bundle_has_space()
|
| H A D | sendmsg.c | 563 p->upgrade = true; in rxrpc_sendmsg_cmsg()
643 cp.upgrade = p->upgrade; in rxrpc_new_client_call_for_sendmsg()
673 .upgrade = false, in rxrpc_do_sendmsg()
|
| H A D | ar-internal.h | 436 bool upgrade; /* T if service ID can be upgraded */ member
510 bool upgrade; /* T if service ID can be upgraded */ member
600 bool upgrade; /* T if service ID can be upgraded */ member
908 bool upgrade; /* If the connection is upgradeable */ member
|
| /linux/arch/powerpc/platforms/powermac/ |
| H A D | Kconfig | 26 bool "Support for powersurge upgrade cards" if EXPERT
35 both dual and quad socket upgrade cards.
|
| /linux/Documentation/scsi/ |
| H A D | FlashPoint.rst | 8 The upgrade program described below has been officially terminated effective
101 the FlashPoint would be able to upgrade to the BT-946C. While this helped
134 has put in place a direct upgrade program to allow any Linux user worldwide
140 upgrade has been set at US $45 plus shipping and handling, and the upgrade
145 As of 14 June 1996, the original BusLogic FlashPoint LT to BT-948 upgrade
149 price for this upgrade has been set at US $65 plus shipping and handling.
168 participate. To summarize, BusLogic is offering Linux users an upgrade
|
| /linux/Documentation/ABI/testing/ |
| H A D | sysfs-driver-ucsi-ccg | 6 firmware upgrade by writing [Yy1] to the file.
|
| /linux/Documentation/admin-guide/ |
| H A D | thunderbolt.rst | 211 Before you upgrade firmware on a device, host or retimer, please make
212 sure it is a suitable upgrade. Failing to do that may render the device
216 Host NVM upgrade on Apple Macs is not supported.
245 from their side, you can use method below to directly upgrade the
256 upgrade process as follows::
281 If the platform supports, it may be possible to upgrade the retimer NVM
284 attributes: ``offline`` and ``rescan``. The way to upgrade the firmware
|
| /linux/fs/xfs/ |
| H A D | Kconfig | 34 should upgrade by backing up their files, reformatting, and restoring
41 upgrade xfsprogs to the latest version and try again.
61 should upgrade by backing up their files, reformatting, and restoring
68 found, please upgrade xfsprogs to the latest version and try again.
|
| /linux/drivers/scsi/device_handler/ |
| H A D | Kconfig | 26 be sent to start it and cannot upgrade the firmware then select y.
|
| /linux/Documentation/admin-guide/acpi/ |
| H A D | initrd_table_override.rst | 11 upgrade the ACPI execution environment that is defined by the ACPI tables
37 allows you to upgrade the buggy tables before your platform/BIOS vendor
|
| /linux/drivers/sbus/char/ |
| H A D | Kconfig | 22 able to upgrade the OBP firmware, say Y here.
|
| /linux/Documentation/filesystems/ |
| H A D | ecryptfs.rst | 35 In the beta/experimental releases of eCryptfs, when you upgrade
|
| /linux/arch/arm/boot/dts/marvell/ |
| H A D | kirkwood-b3.dts | 10 * old. Either upgrade, or consider the following email:
|
| /linux/arch/arm64/boot/dts/marvell/ |
| H A D | armada-3720-gl-mv1000.dts | 16 led-upgrade = &led_power;
|
| /linux/Documentation/driver-api/mtd/ |
| H A D | spi-intel.rst | 25 Below are the steps how to upgrade MinnowBoard MAX BIOS directly from
|
| /linux/arch/arm/boot/dts/gemini/ |
| H A D | gemini-dlink-dir-685.dts | 317 * this is called "upgrade" on the vendor system.
320 label = "upgrade";
|
| /linux/arch/arm/boot/dts/broadcom/ |
| H A D | bcm47094-dlink-dir-890l.dts | 145 * "upgrade" and "rootfs" (probably using OpenWrt
|
| /linux/Documentation/virt/kvm/arm/ |
| H A D | hyp-abi.rst | 66 including an attempt to upgrade the kernel's exception level from
|
| /linux/drivers/message/fusion/ |
| H A D | Kconfig | 85 One use of this ioctl interface is to perform an upgrade (reflash)
|
| /linux/Documentation/ |
| H A D | Changes | 232 You'll probably want to upgrade.
256 debugfs. Obviously, it's a good idea to upgrade.
344 upgrade pppd to at least 2.4.0.
|
| /linux/Documentation/hwmon/ |
| H A D | via686a.rst | 28 upgrade before resorting to this. Does not do a
|
| /linux/drivers/gpu/drm/xe/ |
| H A D | Kconfig | 112 recommended to upgrade to a kernel version with proper support as soon
|
| /linux/Documentation/ABI/stable/ |
| H A D | sysfs-driver-mlxreg-io | 112 due to voltage monitor devices upgrade failure,
241 bios_auth_fail: BIOS upgrade is failed because provided BIOS
244 bios_upgrade_fail: BIOS upgrade is failed by some other
433 upgrade through the JTAG daisy-chain.
812 Description: These files show status of Unified Fabric Manager upgrade.
813 state. 0 - means upgrade is done, 1 - otherwise.
|
| /linux/Documentation/process/ |
| H A D | handling-regressions.rst | 526 have a "upgrade in place" model. We don't have a "upgrade with new
624 The whole point of "we do not regress" is so that people can upgrade
672 And dammit, we upgrade the kernel ALL THE TIME without upgrading any
677 upgrade random other tools that I don't even care about as I develop
681 So no. Your rule is COMPLETELY wrong. If you cannot upgrade a kernel
754 another problem, and as such caused a kernel upgrade to fail for a
|
| /linux/drivers/net/ethernet/fungible/funcore/ |
| H A D | fun_hci.h | 863 } upgrade; member
920 } upgrade; member
|