/openbmc/bmcweb/redfish-core/include/registries/ |
H A D | base_message_registry.hpp | 45 …"Indicates that while attempting to access, connect to, or transfer to or from another resource, t… 52 … "Attempt to ensure that the URI is correct and that the service has the appropriate credentials.", 57 … "Indicates that the account for the session was removed, and so the session was removed as well.", 67 "Indicates that the account was successfully modified.", 77 "Indicates that the modification requested for the account was not successful.", 87 "Indicates that the account was successfully removed.", 109 … "Indicates that the action supplied with the `POST` operation is not supported by the resource.", 121 … "Indicates that the action was supplied with a duplicated action parameter in the request body.", 134 …"Indicates that the action requested was missing an action parameter that is required to process t… 147 … "Indicates that the parameter supplied for the action is not supported on the resource.", [all …]
|
/openbmc/linux/tools/perf/pmu-events/arch/arm64/fujitsu/a64fx/ |
D | other.json |
|
/openbmc/linux/tools/memory-model/Documentation/ |
D | glossary.txt |
|
/openbmc/linux/Documentation/process/ |
D | management-style.rst |
|
D | 6.Followthrough.rst |
|
/openbmc/linux/tools/perf/pmu-events/arch/x86/goldmont/ |
D | cache.json |
|
/openbmc/qemu/docs/devel/migration/ |
H A D | main.rst | 7 QEMU has code to load/save the state of the guest that it is running. 9 that, saves the state for each device that the guest is running. 14 two times. I.e. it can only restore the state in one guest that has 15 the same devices that the one it was saved (this last requirement can 16 be relaxed a bit, but for now we can consider that configuration has 19 Once that we are able to save/restore a guest, a new functionality is 20 requested: migration. This means that QEMU is able to start in one 29 the guest to be stopped. Typically the time that the guest is 31 (notice that this depends on a lot of things). 38 The migration stream is normally just a byte stream that can be passed [all …]
|
/openbmc/linux/tools/perf/pmu-events/arch/x86/knightslanding/ |
D | memory.json |
|
/openbmc/linux/tools/perf/pmu-events/arch/x86/haswell/ |
D | virtual-memory.json |
|
/openbmc/linux/tools/perf/pmu-events/arch/x86/haswellx/ |
D | virtual-memory.json |
|
/openbmc/linux/Documentation/filesystems/ |
D | path-lookup.rst |
|
/openbmc/openbmc/meta-openembedded/meta-oe/licenses/ |
H A D | FLTK | 13 The authors do request that such modifications be 19 2. Widgets that are subclassed from FLTK widgets do not 35 with programs that are linked to the FLTK library, nor 74 price. Our General Public Licenses are designed to make sure that you 76 this service if you wish), that you receive source code or can get it 77 if you want it, that you can change the software or use pieces of it 78 in new free programs; and that you know you can do these things. 80 To protect your rights, we need to make restrictions that forbid 86 or for a fee, you must give the recipients all the rights that we gave 87 you. You must make sure that they, too, receive or can get the source [all …]
|
H A D | Mini-XML-License | 20 with programs that are linked to the Mini-XML library, nor 51 price. Our General Public Licenses are designed to make sure that you 53 this service if you wish), that you receive source code or can get it 54 if you want it, that you can change the software or use pieces of it 55 in new free programs; and that you know you can do these things. 57 To protect your rights, we need to make restrictions that forbid 63 or for a fee, you must give the recipients all the rights that we gave 64 you. You must make sure that they, too, receive or can get the source 66 complete object files to the recipients so that they can relink them 75 that everyone understands that there is no warranty for this free [all …]
|
/openbmc/phosphor-host-ipmid/test/message/ |
H A D | unpack.cpp | 26 // check that the number of bytes matches in TEST() 28 // check that the payload was fully unpacked in TEST() 31 // check that the bytes were correctly unpacked (LSB first) in TEST() 40 // check that the number of bytes matches in TEST() 42 // check that the payload was not fully unpacked in TEST() 45 // check that the bytes were correctly unpacked (LSB first) in TEST() 54 // check that the number of bytes matches in TEST() 56 // check that the payload was not fully unpacked (comprehends unpack errors) in TEST() 58 // check that v is zero in TEST() 67 // check that the number of bytes matches in TEST() [all …]
|
/openbmc/linux/tools/perf/pmu-events/arch/x86/silvermont/ |
D | cache.json |
|
/openbmc/linux/LICENSES/preferred/ |
D | LGPL-2.1 |
|
D | LGPL-2.0 |
|
/openbmc/openbmc/poky/meta/files/common-licenses/ |
H A D | LGPL-2.1-or-later | 31 Our General Public Licenses are designed to make sure that you have the freedom 33 wish); that you receive source code or can get it if you want it; that you 34 can change the software and use pieces of it in new free programs; and that 35 you are informed that you can do these things. 37 To protect your rights, we need to make restrictions that forbid distributors 43 a fee, you must give the recipients all the rights that we gave you. You must 44 make sure that they, too, receive or can get the source code. If you link 46 recipients, so that they can relink them with the library after making changes 54 To protect each distributor, we want to make it very clear that there is no 56 else and passed on, the recipients should know that what they have is not [all …]
|
H A D | LGPL-2.1-only | 20 …that you have the freedom to distribute copies of free software (and charge for this service if yo… 22 To protect your rights, we need to make restrictions that forbid distributors to deny you these rig… 24 …that we gave you. You must make sure that they, too, receive or can get the source code. If you li… 28 …that there is no warranty for the free library. Also, if the library is modified by someone else a… 30 …that a company cannot effectively restrict the users of a free program by obtaining a restrictive … 38 …ary, so that it becomes a de-facto standard. To achieve this, non-free programs must be allowed to… 42 …reedom, it does ensure that the user of a program that is linked with the Library has the freedom … 44 …ntion to the difference between a "work based on the library" and a "work that uses the library". … 52 …ary" means either the Library or any derivative work under copyright law: that is to say, a work c… 56 …brary in a tool for writing it). Whether that is true depends on what the Library does and what th… [all …]
|
H A D | LGPL-2.0-or-later | 25 General Public Licenses are designed to make sure that you have the freedom 27 wish), that you receive source code or can get it if you want it, that you 28 can change the software or use pieces of it in new free programs; and that 31 To protect your rights, we need to make restrictions that forbid anyone to 37 a fee, you must give the recipients all the rights that we gave you. You must 38 make sure that they, too, receive or can get the source code. If you link 40 recipients so that they can relink them with the library, after making changes 48 Also, for each distributor's protection, we want to make certain that everyone 49 understands that there is no warranty for this free library. If the library 51 that what they have is not the original version, so that any problems introduced [all …]
|
H A D | LGPL-2.0-only | 35 …that you have the freedom to distribute copies of free software (and charge for this service if yo… 39 To protect your rights, we need to make restrictions that forbid anyone to deny you these rights or… 43 …that we gave you. You must make sure that they, too, receive or can get the source code. If you li… 51 …that everyone understands that there is no warranty for this free library. If the library is modif… 55 …that companies distributing free software will individually obtain patent licenses, thus in effect… 59 …erent from the ordinary one; be sure to read it in full, and don't assume that anything in it is t… 63 The reason we have a separate public license for some libraries is that they blur the distinction w… 67 … sharing, because most developers did not use the libraries. We concluded that weaker conditions m… 71 …that are incorporated in them. (We have not seen how to achieve this as regards changes in header … 75 …ntion to the difference between a "work based on the library" and a "work that uses the library". … [all …]
|
/openbmc/u-boot/Licenses/ |
H A D | lgpl-2.1.txt | 28 not price. Our General Public Licenses are designed to make sure that 30 for this service if you wish); that you receive source code or can get 31 it if you want it; that you can change the software and use pieces of 32 it in new free programs; and that you are informed that you can do 35 To protect your rights, we need to make restrictions that forbid 41 or for a fee, you must give the recipients all the rights that we gave 42 you. You must make sure that they, too, receive or can get the source 44 complete object files to the recipients, so that they can relink them 52 To protect each distributor, we want to make it very clear that 55 that what they have is not the original version, so that the original [all …]
|
H A D | lgpl-2.0.txt | 25 price. Our General Public Licenses are designed to make sure that you 27 this service if you wish), that you receive source code or can get it 28 if you want it, that you can change the software or use pieces of it 29 in new free programs; and that you know you can do these things. 31 To protect your rights, we need to make restrictions that forbid 37 or for a fee, you must give the recipients all the rights that we gave 38 you. You must make sure that they, too, receive or can get the source 40 complete object files to the recipients so that they can relink them 49 that everyone understands that there is no warranty for this free 51 want its recipients to know that what they have is not the original [all …]
|
/openbmc/linux/Documentation/networking/devlink/ |
D | devlink-trap.rst |
|
/openbmc/linux/Documentation/maintainer/ |
D | rebasing-and-merging.rst |
|