Package: linux-headers-5.2.0-2-common:amd64 (5.2.7-1, automatic),
linux-image-5.2.0-2-amd64:amd64 (5.2.7-1, automatic),
linux-headers-5.2.0-2-amd64:amd64 (5.2.7-1, automatic), linux-kbuild-5.2:amd64
(5.2.7-1, automatic)
Severity: important
Dear Maintainer,
Kernel was upgraded to 5.2.0-2 on
On Tue, 2019-08-13 at 18:25 +0300, Alper Nebi Yasak wrote:
> Hello. I've opened some more merge requests on salsa for this device.
> I'd appreciate if you could review them.
Thanks. I will probably look at these later in the week.
> Include modules for Chromebook Plus display:
>
This problem is still present in buster.
The relevant strace output seems to be:
capget({version=_LINUX_CAPABILITY_VERSION_3, pid=0}, NULL) = 0
capset({version=_LINUX_CAPABILITY_VERSION_3, pid=0}, {effective=0, permitted=0,
inheritable=0}) = 0
access("/var/lib/nfs/nfsdcltrack", W_OK) = -1 ENOENT
On Tue, Aug 13, 2019 at 7:14 AM Daniel Borkmann wrote:
>
> On 8/13/19 2:24 PM, Jiri Olsa wrote:
> > On Mon, Aug 12, 2019 at 07:04:12PM +, Julia Kartseva wrote:
> >> I would like to bring up libbpf publishing discussion started at [1].
> >> The present state of things is that libbpf is built
On Tue, Aug 13, 2019 at 5:26 AM Jiri Olsa wrote:
>
> On Mon, Aug 12, 2019 at 07:04:12PM +, Julia Kartseva wrote:
> > I would like to bring up libbpf publishing discussion started at [1].
> > The present state of things is that libbpf is built from kernel tree, e.g.
> > [2]
> > For Debian and
Hello. I've opened some more merge requests on salsa for this device.
I'd appreciate if you could review them.
Include modules for Chromebook Plus display:
https://salsa.debian.org/kernel-team/initramfs-tools/merge_requests/15
hook-functions: Handle spi-rockchip hidden dependency on pl330:
On 8/13/19 2:24 PM, Jiri Olsa wrote:
On Mon, Aug 12, 2019 at 07:04:12PM +, Julia Kartseva wrote:
I would like to bring up libbpf publishing discussion started at [1].
The present state of things is that libbpf is built from kernel tree, e.g. [2]
For Debian and [3] for Fedora whereas the
On Mon, Aug 12, 2019 at 07:04:12PM +, Julia Kartseva wrote:
> I would like to bring up libbpf publishing discussion started at [1].
> The present state of things is that libbpf is built from kernel tree, e.g. [2]
> For Debian and [3] for Fedora whereas the better way would be having a
>
8 matches
Mail list logo