Home
last modified time | relevance | path

Searched refs:had (Results 1 – 25 of 37) sorted by relevance

12

/f-stack/app/nginx-1.16.1/
H A DCHANGES174 had appeared in 1.13.5.
1267 had appeared in 1.7.11.
1667 had appeared in 1.5.6.
2005 had appeared in 1.3.14.
3105 had appeared in 0.9.3.
4000 had appeared in 0.8.9.
4042 had appeared in 0.7.7.
4871 had appeared in 0.7.0.
4991 had appeared in 0.7.4.
4994 had appeared in 0.7.3.
[all …]
/f-stack/freebsd/contrib/openzfs/.github/
H A Dstale.yml22 This issue has been automatically marked as "stale" because it has not had
H A DCONTRIBUTING.md274 If someone else had part in your pull request, please add the following to the commit:
/f-stack/freebsd/contrib/zlib/
H A Dgzread.c182 unsigned had; local
186 had = strm->avail_out;
215 state->x.have = had - strm->avail_out;
/f-stack/tools/libxo/doc/
H A Dfaq.rst45 how to render that XML into text. ODL might had a set of tags
107 In moving these ideas to bsd, two things had to happen: the
108 formatting had to happen at the source since BSD won't have
/f-stack/freebsd/contrib/zstd/zlibWrapper/
H A Dgzread.c191 unsigned had; local
195 had = strm->avail_out;
224 state.state->x.have = had - strm->avail_out;
/f-stack/freebsd/contrib/device-tree/Bindings/clock/
H A Dqcom,sdm845-dispcc.yaml23 # The code had to use hardcoded mechanisms to find the input clocks.
/f-stack/freebsd/contrib/zlib/contrib/asm686/
H A DREADME.68640 gcc's generated code had caught up with it sometime around gcc 2.95
/f-stack/freebsd/contrib/device-tree/Bindings/i2c/
H A Dmarvell,mv64xxx-i2c.yaml42 version of the SoC which had broken offload support. Linux
H A Di2c-pxa-pci-ce4100.txt22 non-zero if you had 2 or more devices mapped off
/f-stack/app/nginx-1.16.1/auto/cc/
H A Dsunc78 # older versions had problems with bit-fields
/f-stack/freebsd/contrib/zlib/doc/
H A Dalgorithm.txt76 table took no time (and if you had infinite memory), then there would only
108 will be two lookups. If you had a compression method with really long
181 So what we have here are three tables with a total of 20 entries that had to
/f-stack/freebsd/contrib/device-tree/Bindings/serial/
H A Dnvidia,tegra20-hsuart.txt38 -4 to +4 %. All Tegra devices till Tegra210 had this support. However,
/f-stack/freebsd/contrib/device-tree/Bindings/display/
H A Darm,pl11x.txt45 The port's endbpoint subnode had this, now deprecated property
/f-stack/app/nginx-1.16.1/auto/os/
H A Dlinux29 # posix_fadvise64() had been implemented in 2.5.60
/f-stack/dpdk/doc/guides/prog_guide/
H A Dstack_lib.rst83 In this case thread A would not detect that the list had changed, and would
/f-stack/freebsd/netinet/libalias/
H A DHISTORY117 had to be closed when a binding failed. Problem
/f-stack/app/redis-5.0.5/deps/hiredis/
H A DCHANGELOG.md34 Previously it broke some builds for people that had `DEBUG` set to some arbitrary value,
/f-stack/freebsd/contrib/device-tree/Bindings/power/
H A Drockchip-io-domain.txt22 If there were some other software that had the smarts of making
/f-stack/dpdk/doc/guides/rel_notes/
H A Drelease_16_04.rst231 Previously szedata2 device had to be added by ``--vdev`` option.
407 that case, preventing the caller from knowing if the object had to be freed
416 that case, preventing the caller from knowing if the object had to be freed
H A Drelease_2_1.rst120 operation on VFs. In such cases, joined multicast addresses had to be added
396 Some test rules had equal priority for the same category. That could cause
461 A function in ``cmdline.c`` had a return that did not free the buf properly.
607 worked with PF, but had problems with VF since it has less queues than PF.
/f-stack/dpdk/doc/guides/nics/
H A Dnetvsc.rst79 On older kernels, the same effect can be had by manual sysfs bind and unbind
/f-stack/app/redis-5.0.5/deps/lua/
H A DHISTORY141 semantics of Lua. Whereas fallbacks had a global nature, tag methods
/f-stack/app/redis-5.0.5/deps/linenoise/
H A DREADME.markdown20 … using a configure script not supporting line editing at all (A problem we had with Redis-cli for …
/f-stack/app/redis-5.0.5/deps/jemalloc/
H A DChangeLog349 testing, thanks to @davidtgoldblatt. Had we had this testing infrastructure
579 - Fix run quantization. In practice this bug had no impact unless
934 bugs had no impact except for malformed inputs.
936 existing calls, so they had no impact.

12