Searched refs:longterm (Results 1 – 9 of 9) sorted by relevance
/openbmc/linux/drivers/media/v4l2-core/ |
H A D | v4l2-h264.c | 60 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 …]
|
/openbmc/linux/include/media/ |
H A D | v4l2-h264.h | 38 u16 longterm : 1; member
|
/openbmc/linux/Documentation/admin-guide/ |
H A D | reporting-issues.rst | 12 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 D | reporting-regressions.rst | 100 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 D | quickly-build-trimmed-linux.rst | 148 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:
|
/openbmc/linux/Documentation/process/ |
H A D | handling-regressions.rst | 159 mainline, stable, or longterm release (either directly or via backport). 172 particular hardware environment, distribution, or stable/longterm series. 175 into a recent mainline, stable, or longterm release (either directly or via 203 know such a regression made it into a mainline, stable, or longterm release. 217 Regarding stable and longterm kernels: 225 in case you know the culprit was backported to stable or longterm kernels. 227 * When receiving reports about regressions in recent stable or longterm kernel 233 into a proper mainline, stable, or longterm release, fix it quickly in 376 repositories of linux-next, mainline, and stable/longterm.
|
/openbmc/linux/Documentation/core-api/ |
H A D | pin_user_pages.rst | 152 NOTE: Some pages, such as DAX pages, cannot be pinned with longterm pins. That's 223 will be pinned longterm, and whose data will be accessed.
|
/openbmc/linux/Documentation/bpf/ |
H A D | bpf_devel_QA.rst | 409 The current stable and longterm stable kernels are all listed here:
|
/openbmc/linux/Documentation/filesystems/ |
H A D | porting.rst | 869 clone_private_mount() returns a longterm mount now, so the proper destructor of
|