Home
last modified time | relevance | path

Searched refs:longterm (Results 1 – 13 of 13) sorted by relevance

/linux-6.15/drivers/media/v4l2-core/
H A Dv4l2-h264.c60 b->refs[i].longterm = true; in v4l2_h264_init_reflist_builder()
138 if (builder->refs[idxa].longterm != builder->refs[idxb].longterm) { in v4l2_h264_p_ref_list_cmp()
140 if (!builder->refs[idxa].longterm) in v4l2_h264_p_ref_list_cmp()
154 if (!builder->refs[idxa].longterm) in v4l2_h264_p_ref_list_cmp()
177 if (builder->refs[idxa].longterm != builder->refs[idxb].longterm) { in v4l2_h264_b0_ref_list_cmp()
186 if (builder->refs[idxa].longterm) in v4l2_h264_b0_ref_list_cmp()
222 if (builder->refs[idxa].longterm != builder->refs[idxb].longterm) { in v4l2_h264_b1_ref_list_cmp()
231 if (builder->refs[idxa].longterm) in v4l2_h264_b1_ref_list_cmp()
318 bool longterm = builder->refs[reflist[i].index].longterm; in format_ref_list_p() local
356 bool longterm = builder->refs[reflist[i].index].longterm; in format_ref_list_b() local
[all …]
/linux-6.15/include/media/
H A Dv4l2-h264.h38 u16 longterm : 1; member
/linux-6.15/Documentation/admin-guide/
H A Dverify-bugs-and-bisect-regressions.rst261 even if you face a problem with a kernel from a 'stable/longterm' series
322 * Something regressed when updating from a stable/longterm release
324 stable/longterm version based on one (say 6.1.5)? Then consider the
331 a later one (like 6.1-rc1) or a stable/longterm release based on it
335 * Something regressed when updating within a stable/longterm series (say
384 preparing things to add branches for stable/longterm series later::
870 * Did you face a regression within a stable/longterm series (say between
882 If you bisected a regression within a stable/longterm series that also
1595 distributor or face a regression within a stable/longterm series. But it's
1840 Check the kernel built from the latest stable/longterm codebase
[all …]
H A Dreporting-issues.rst12 longterm series? One still supported? Then search the `LKML
30 supported stable or longterm series as well? Then install its latest release.
101 * If you are facing a regression within a stable or longterm version line
103 'Dealing with regressions within a stable and longterm kernel line'.
130 stable and longterm kernels.
168 Reporting regressions within a stable and longterm kernel line
216 within a stable and longterm kernel line" above.
574 Regression in stable or longterm kernel?
929 stable and longterm kernels.*
1468 a regression within a stable and longterm kernel line.
[all …]
H A Dreporting-regressions.rst100 If it's a regression within a stable or longterm series (e.g.
181 updating attractive: they don't want users to stay on stable or longterm Linux
207 Greg Kroah-Hartman et al. for various stable/longterm series.
H A Dquickly-build-trimmed-linux.rst148 In case you want to access a stable/longterm release (say v6.1.5), simply add
163 pre-release like ``v6.2-rc1`` will work, too. Stable or longterm versions
165 stable/longterm branch as described.
290 In case you want to build a version from a stable/longterm series you have
521 like ``--depth=1``, unless you add branches for stable/longterm kernels.
629 stable/longterm releases. This approach has just one downside:
H A Dbug-bisect.rst102 you bisected a stable or longterm kernel series, in which case you want to
/linux-6.15/Documentation/process/
H A Dhandling-regressions.rst166 mainline, stable, or longterm release (either directly or via backport).
179 particular hardware environment, distribution, or stable/longterm series.
182 into a recent mainline, stable, or longterm release (either directly or via
210 know such a regression made it into a mainline, stable, or longterm release.
224 Regarding stable and longterm kernels:
232 in case you know the culprit was backported to stable or longterm kernels.
234 * When receiving reports about regressions in recent stable or longterm kernel
240 into a proper mainline, stable, or longterm release, fix it quickly in
382 repositories of linux-next, mainline, and stable/longterm.
/linux-6.15/Documentation/core-api/
H A Dpin_user_pages.rst152 NOTE: Some pages, such as DAX pages, cannot be pinned with longterm pins. That's
225 will be pinned longterm, and whose data will be accessed.
/linux-6.15/Documentation/admin-guide/mm/
H A Dhugetlbpage.rst390 scenarios: memory offline, memory failure, longterm pinning, syscalls(mbind,
/linux-6.15/Documentation/bpf/
H A Dbpf_devel_QA.rst417 The current stable and longterm stable kernels are all listed here:
/linux-6.15/Documentation/filesystems/
H A Dporting.rst869 clone_private_mount() returns a longterm mount now, so the proper destructor of
/linux-6.15/Documentation/translations/sp_SP/process/
H A Dhandling-regressions.rst369 también las de los repositorios linux-next, mainline y stable/longterm.