search for: buildon

...|-- i386-allyesconfig | |-- drivers-gpu-drm-nouveau-nvkm-subdev-gsp-r535.c:warning:Function-parameter-or-struct-member-gsp-not-described-in-nvkm_gsp_radix3_sg | `-- fs-ubifs-journal.c:warning:expecting-prototype-for-wake_up_reservation().-Prototype-was-for-add_or_start_queue()-instead |-- i386-buildonly-randconfig-002-20240307 | `-- fs-ubifs-journal.c:warning:expecting-prototype-for-wake_up_reservation().-Prototype-was-for-add_or_start_queue()-instead |-- i386-buildonly-randconfig-004-20240307 | `-- drivers-gpu-drm-nouveau-nvkm-subdev-gsp-r535.c:warning:Function-parameter-or-struct-member-gs...

...ting-bytes-into-a-region-of-size-between-and |-- i386-allmodconfig | `-- drivers-regulator-rtq2208-regulator.c:warning:rtq2208_regulator_ldo_ops-defined-but-not-used |-- i386-allyesconfig | `-- drivers-regulator-rtq2208-regulator.c:warning:rtq2208_regulator_ldo_ops-defined-but-not-used |-- i386-buildonly-randconfig-002-20240529 | `-- drivers-regulator-rtq2208-regulator.c:warning:rtq2208_regulator_ldo_ops-defined-but-not-used |-- i386-buildonly-randconfig-003-20240529 | `-- drivers-regulator-rtq2208-regulator.c:warning:rtq2208_regulator_ldo_ops-defined-but-not-used |-- i386-buildonly-randconfi...

...-or-more-bytes-at-offsets-and-overlaps-bytes-at-offset |-- sh-allmodconfig | `-- drivers-pwm-pwm-stm32.c:error:implicit-declaration-of-function-devm_clk_rate_exclusive_get |-- sh-allyesconfig | `-- drivers-pwm-pwm-stm32.c:error:implicit-declaration-of-function-devm_clk_rate_exclusive_get |-- sh-buildonly-randconfig-r003-20221218 | `-- standard-input:Error:unknown-pseudo-op:cfi_restore_st |-- sparc-allmodconfig | |-- mm-mempolicy.c:warning:expecting-prototype-for-alloc_pages_mpol_noprof().-Prototype-was-for-alloc_pages_mpol()-instead | |-- mm-mempolicy.c:warning:expecting-prototype-for-alloc...

...rror:implicit-declaration-of-function-unxlate_dev_mem_ptr |-- sh-sh7710voipgw_defconfig | `-- drivers-char-mem.c:error:implicit-declaration-of-function-unxlate_dev_mem_ptr |-- sparc-randconfig-r005-20230704 | `-- drivers-bluetooth-btmtk.c:error:struct-hci_dev-has-no-member-named-dump `-- x86_64-buildonly-randconfig-r003-20230703 `-- drivers-bluetooth-btmtk.c:error:struct-hci_dev-has-no-member-named-dump clang_recent_errors |-- arm64-randconfig-r033-20230704 | `-- drivers-mfd-max77541.c:warning:cast-to-smaller-integer-type-enum-max7754x_ids-from-const-void |-- hexagon-randconfig-r041-2023070...

...gulator-rtq2208-regulator.c:warning:rtq2208_regulator_ldo_ops-defined-but-not-used |-- um-allyesconfig | |-- drivers-regulator-rtq2208-regulator.c:warning:rtq2208_regulator_ldo_ops-defined-but-not-used | `-- kernel-bpf-verifier.c:error:pcpu_hot-undeclared-(first-use-in-this-function) |-- x86_64-buildonly-randconfig-001-20240523 | `-- drivers-regulator-rtq2208-regulator.c:warning:rtq2208_regulator_ldo_ops-defined-but-not-used |-- x86_64-buildonly-randconfig-002-20240523 | `-- drivers-regulator-rtq2208-regulator.c:warning:rtq2208_regulator_ldo_ops-defined-but-not-used |-- x86_64-randconfig-001-...

...efconfig gcc hexagon randconfig-r001-20230731 clang hexagon randconfig-r022-20230731 clang hexagon randconfig-r041-20230731 clang hexagon randconfig-r045-20230731 clang i386 allyesconfig gcc i386 buildonly-randconfig-r004-20230731 gcc i386 buildonly-randconfig-r005-20230731 gcc i386 buildonly-randconfig-r006-20230731 gcc i386 debian-10.3 gcc i386 defconfig gcc i386 randconfig-i001-2023073...

...er-node_id-not-described-in-mempool_create_node |-- i386-allyesconfig | |-- mm-mempool.c:warning:Function-parameter-or-struct-member-gfp_mask-not-described-in-mempool_create_node | `-- mm-mempool.c:warning:Function-parameter-or-struct-member-node_id-not-described-in-mempool_create_node |-- i386-buildonly-randconfig-001-20240403 | |-- mm-mempool.c:warning:Function-parameter-or-struct-member-gfp_mask-not-described-in-mempool_create_node | `-- mm-mempool.c:warning:Function-parameter-or-struct-member-node_id-not-described-in-mempool_create_node |-- i386-buildonly-randconfig-005-20240403 | |-- m...

...efconfig clang hexagon randconfig-001-20240411 clang hexagon randconfig-002-20240411 clang i386 allmodconfig gcc i386 allnoconfig gcc i386 allyesconfig gcc i386 buildonly-randconfig-001-20240411 clang i386 buildonly-randconfig-002-20240411 clang i386 buildonly-randconfig-003-20240411 clang i386 buildonly-randconfig-004-20240411 clang i386 buildonly-randconfig-005-20240411 clang i386 buildonly-randconfig-006-2024041...

...lish. > I did a draft of xen 4.4 packages for debian starting from 4.4.0-0ubuntu5 plus some changes. I included the close of some bugs in changelog but surely there will be more resolved to be added. I tested build on sid and was successfull. During the week when I have time I'll make the buildon a clean sid and I'll test thepackages. I'll probably do other improvements. The draft I did with all changes are here: https://github.com/Fantu/pkg-xen/tree/debian-next Any feedback is appreciated. -------------- next part -------------- A non-text attachment was scrubbed... Name: smime...

...lish. > I did a draft of xen 4.4 packages for debian starting from 4.4.0-0ubuntu5 plus some changes. I included the close of some bugs in changelog but surely there will be more resolved to be added. I tested build on sid and was successfull. During the week when I have time I'll make the buildon a clean sid and I'll test thepackages. I'll probably do other improvements. The draft I did with all changes are here: https://github.com/Fantu/pkg-xen/tree/debian-next Any feedback is appreciated. -------------- next part -------------- A non-text attachment was scrubbed... Name: smime...

...of xen 4.4 packages for debian starting from > 4.4.0-0ubuntu5 plus some changes. > I included the close of some bugs in changelog but surely there will > be more resolved to be added. > I tested build on sid and was successfull. > During the week when I have time I'll make the buildon a clean sid and > I'll test thepackages. > I'll probably do other improvements. > > The draft I did with all changes are here: > https://github.com/Fantu/pkg-xen/tree/debian-next > > Any feedback is appreciated. > I could not try it on sid because it is not install...

...of xen 4.4 packages for debian starting from > 4.4.0-0ubuntu5 plus some changes. > I included the close of some bugs in changelog but surely there will > be more resolved to be added. > I tested build on sid and was successfull. > During the week when I have time I'll make the buildon a clean sid and > I'll test thepackages. > I'll probably do other improvements. > > The draft I did with all changes are here: > https://github.com/Fantu/pkg-xen/tree/debian-next > > Any feedback is appreciated. > I could not try it on sid because it is not install...

Il 03/05/2014 11:30, Fabio Fantoni ha scritto: >> On Thu, 2014-03-06 at 14:05 +0000, Ian Campbell wrote: >> > Hi waldi, >> > >> > Are you planning to update the Xen package too 4.4 soon? Upstream have >> > released 4.4-rc6 and AIUI are planning to release the final version >> next >> > week (I've been out of the office for a bit, so I

Il 03/05/2014 11:30, Fabio Fantoni ha scritto: >> On Thu, 2014-03-06 at 14:05 +0000, Ian Campbell wrote: >> > Hi waldi, >> > >> > Are you planning to update the Xen package too 4.4 soon? Upstream have >> > released 4.4-rc6 and AIUI are planning to release the final version >> next >> > week (I've been out of the office for a bit, so I

> On Thu, 2014-03-06 at 14:05 +0000, Ian Campbell wrote: > > Hi waldi, > > > > Are you planning to update the Xen package too 4.4 soon? Upstream have > > released 4.4-rc6 and AIUI are planning to release the final version next > > week (I've been out of the office for a bit, so I don't know the precise > > state, but that was the last I heard). >

> On Thu, 2014-03-06 at 14:05 +0000, Ian Campbell wrote: > > Hi waldi, > > > > Are you planning to update the Xen package too 4.4 soon? Upstream have > > released 4.4-rc6 and AIUI are planning to release the final version next > > week (I've been out of the office for a bit, so I don't know the precise > > state, but that was the last I heard). >

Now that we're supporting things like Ada and the GSP, there's situations where we really need to actually know the display state that we're starting with when loading the driver in order to prevent breaking GSP expectations. The first step in doing this is making it so that we can read the current state of IORs from nvkm in DRM, so that we can fill in said into into the atomic state.