Home
last modified time | relevance | path

Searched full:however (Results 1 – 25 of 6493) sorted by relevance

12345678910>>...260

/OK3568_Linux_fs/kernel/drivers/scsi/mpt3sas/
H A DKconfig32 # DAMAGES (INCLUDING WITHOUT LIMITATION LOST PROFITS), HOWEVER CAUSED AND
60 MAX_PHYS_SEGMENTS in most kernels. However in SuSE kernels this
61 can be 256. However, it may decreased down to 16. Decreasing this
72 MAX_PHYS_SEGMENTS in most kernels. However in SuSE kernels this
73 can be 256. However, it may decreased down to 16. Decreasing this
/OK3568_Linux_fs/kernel/Documentation/powerpc/
H A Dpmu-ebb.rst34 events, however unless the target process enables EBBs (via mtspr(BESCR)) no
48 It is however safe to run 'perf' commands on a process which is using EBBs. The
94 However, due to the design of the perf_events API, enabling an event does not
102 this case the enable will be successful. However if there is already an event
109 It is possible to read() from an EBB event. However the results are
125 The EBB handler is just regular userspace code, however it must be written in
/OK3568_Linux_fs/external/chromium/licenses/
H A DNOTICE22 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
53 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
81 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
123 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
152 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
229 OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED
273 OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED
302 OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED
330 OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED
374 OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED
[all …]
H A DLICENSE.4570 * HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
131 * HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
188 in BoringSSL (i.e. libcrypto and libssl) when compiled, however, so
214 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
248 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
/OK3568_Linux_fs/yocto/poky/meta/files/common-licenses/
H A DNet-SNMP21 …DS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY…
31 …DS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY…
51 …DS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY…
61 …DS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY…
71 …DS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY…
85 …DS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY…
97 …DS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY…
107 …DS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY…
H A DSleepycat32 INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
59 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
86 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
H A DDOC3 …ell as copy and distribute modified versions of this software. You must, however, include this cop…
5 …stribute any of your source code that is built using DOC software. Note, however, that you may not…
9 … companies around the world provide commercial support for DOC software, however. DOC software is …
/OK3568_Linux_fs/kernel/Documentation/vm/
H A Dhugetlbfs_reserv.rst20 kernel, the code has evolved over time. However, the basic idea was to
141 always the value (to - from). However, for shared mappings it is possible that
155 However, within those routines the code is simply checking to ensure there
206 However, in every case the avoid_reserve argument overrides the use of
244 in the reserve map already existed so no change is made. However, if there
323 However, if reserves are associated with the subpool a return value less
408 return value of region_chg(). However, in the case of shared mappings it is
438 indicate that there is a reservation for the page. However, the subpool and
463 in the section "Reservation Map Modifications". However, they do take into
525 However, there are several instances where errors are encountered after a huge
[all …]
/OK3568_Linux_fs/buildroot/package/ibrcommon/
H A D0001-ibrcommon-data-File.cpp-support-POSIX-basename-call.patch11 However, this leads to a second problem. POSIX defines the function as
13 However, the std::string.cstr() method returns a const char*.
15 POSIX says that the string parameter can be modified. However the GNU
/OK3568_Linux_fs/kernel/Documentation/filesystems/
H A Dfscrypt.rst30 However, except for filenames, fscrypt does not encrypt filesystem
110 However, fscrypt allows encryption keys to be removed from the kernel,
120 However, these ioctls have some limitations:
142 to your kernel command line. However, this has a performance cost.
352 per-file encryption keys. However, it depends on the security of two
361 to individual filesystems. However, authenticated encryption (AE)
402 However, each encrypted directory still uses a unique key, or
414 >= 16 bytes; cipher block alignment is not required. However,
504 FS_IOC_SET_ENCRYPTION_POLICY is executed. However, it must be added
535 FS_IOC_SET_ENCRYPTION_POLICY is executing. However, if the new
[all …]
H A Dfsverity.rst44 However, because fs-verity makes retrieving the file hash extremely
55 A standard file hash could be used instead of fs-verity. However,
73 authenticating the files is up to userspace. However, to meet some
134 FS_IOC_ENABLE_VERITY checks for write access to the inode. However,
322 one of these things will fail with EPERM. However, changes to
391 the original file size. However, for small files, the padding is
458 However, with this mechanism, userspace programs still need to check
573 Merkle tree from the data page to the root hash. However, for
583 reading a previous data page. However, random reads perform worse.
589 the pagecache, so the above subsection applies too. However, they
[all …]
/OK3568_Linux_fs/kernel/drivers/misc/echo/
H A Decho.h41 well. However, it only works well for signals of constant amplitude. It works
48 FAP, etc. Some perform significantly better than NLMS. However, factors such
53 the NLMS algorithm works very well. However, speech has more low frequency than
96 assess whether that signal contains a strong far end component. However, by the
/OK3568_Linux_fs/kernel/Documentation/arm64/
H A Dperf.rst74 non-VHE guest however please note that EL2 is never counted within a guest.
81 transition at EL2 - however there is a period of time between
85 exclude_host. However when using !exclude_hv there is a small blackout
/OK3568_Linux_fs/yocto/poky/documentation/migration-guides/
H A Dmigration-general.rst35 that everything works for the new release. However, this is not the
42 them much more manageable. However, sometimes it is not practical to
51 releases. However, if the append file is specific to a
H A Dmigration-3.0.rst18 settings to continue working. However, it is advisable to explicitly set
28 layer if needed. However, presently LSB support has been removed from
169 continue to work, however it may be removed in a future release.
239 starting with ``#!/bin/bash`` but has no dependency on bash. However,
276 required. However, if for some reason the software being built by one
/OK3568_Linux_fs/u-boot/include/configs/
H A Dintegrator-common.h45 * However it may be needed if Integrator/CP switch S2-1
55 * However, the default U-Boot code also performs the initialization.
65 * However, the default U-Boot code performs the relocation check,
/OK3568_Linux_fs/kernel/Documentation/hid/
H A Dhid-transport.rst95 multiplex all four on a single physical channel. However, in this document we
160 return the current report state of the device. However, OUTPUT reports as
165 according to the given data. Any of the 3 report types can be used. However,
168 A device must answer with a synchronous acknowledgement. However, HID core
239 drivers can choose to setup their device in this callback. However, normally
262 However, once ->open() is called, transport drivers must be ready for I/O.
274 ->open() calls have been followed by a ->close() call. However, ->start() may
/OK3568_Linux_fs/kernel/Documentation/power/
H A Dpci.rst35 completely inactive. However, when it is necessary to use the device once
53 to put the device that sent it into the full-power state. However, the PCI Bus
63 preparing the device to generate wakeup signals. In that case, however, it
87 in that state. However, the higher the number, the longer the latency for
98 PCI bus power management, however, is not supported by the Linux kernel at the
143 system-specific. However, if the system in question is compliant with the
186 However, quite often the power states of devices are changed during a
234 Usually, however, GPEs are also triggered when the system is in the working
264 BIOS, however, is not required to allow the kernel to control these registers
354 however, this functionality is limited to a few basic operations carried out
[all …]
/OK3568_Linux_fs/kernel/include/linux/
H A Drculist_nulls.h29 * hlist_nulls_del_rcu(), running on this same list. However, it is
70 * However, it is perfectly legal to run concurrently with
93 * However, it is perfectly legal to run concurrently with
124 * However, it is perfectly legal to run concurrently with
/OK3568_Linux_fs/yocto/meta-clang/
H A DREADME.md38 Note that by default gcc will remain the system compiler, however if you wish
57 runtime support. However it's possible to use LLVM runtime to replace it where
74 Using RUNTIME variable will select which C++ runtime is used, however it can be overridden
90 compilation as well as runtime. However, it's up to distribution policies to decide which runtime
/OK3568_Linux_fs/kernel/Documentation/block/
H A Ddata-integrity.rst9 protect against data corruption. However, the detection of the
39 controller and storage device. However, many controllers actually
72 errors. However, the strength is really in the separation of the data
91 device. However, at the same time this is also the biggest
100 However, this level of detail is required when preparing the
/OK3568_Linux_fs/kernel/arch/alpha/include/uapi/asm/
H A Dtypes.h9 * not a major issue. However, for interoperability, libraries still
18 * However, some user programs are fine with this. They can
/OK3568_Linux_fs/kernel/Documentation/timers/
H A Dno_hz.rst52 However, if you are instead running a light workload with long idle
176 However, the drawbacks listed above mean that adaptive ticks should not
236 dyntick-idle mode, an option that most of them take. However,
250 However, please note that use of this parameter can cause
272 interrupt to this CPU. However, the current implementation
286 if needed, however, due to the complexity of reconfiguring RCU at
/OK3568_Linux_fs/kernel/Documentation/devicetree/
H A Dusage-model.rst37 however, of creating a new binding without first doing some homework
136 compatibility with the original Beagle board. However, one should be
160 if they all use the same SoC, or same family of SoCs. However,
179 However, this approach does not take into account the priority of the
325 However, looking at the tree, it is not immediately obvious what kind
398 always be traversed. However, we pass it in as an argument so that
409 used to represent Primecell devices. However, the fiddly bit is that
/OK3568_Linux_fs/kernel/drivers/hwmon/occ/
H A DKconfig13 On-Chip Controller (OCC) on a POWER8 processor. However, this driver
28 On-Chip Controller (OCC) on a POWER9 processor. However, this driver

12345678910>>...260