Processing commands for cont...@bugs.debian.org:
> severity 996170 important
Bug #996170 [src:linux] linux: FTBFS if bpftool detects clang-bpf-co-re
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
996170: https://bugs.deb
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sun, 10 Oct 2021 19:07:34 +0200
Source: linux-signed-i386
Architecture: source
Version: 5.10.70+1~bpo10+1
Distribution: buster-backports
Urgency: medium
Maintainer: Debian Kernel Team
Changed-By: Ben Hutchings
Change
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sun, 10 Oct 2021 19:07:34 +0200
Source: linux-signed-arm64
Architecture: source
Version: 5.10.70+1~bpo10+1
Distribution: buster-backports
Urgency: medium
Maintainer: Debian Kernel Team
Changed-By: Ben Hutchings
Chang
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sun, 10 Oct 2021 19:07:34 +0200
Source: linux-signed-amd64
Architecture: source
Version: 5.10.70+1~bpo10+1
Distribution: buster-backports
Urgency: medium
Maintainer: Debian Kernel Team
Changed-By: Ben Hutchings
Chang
Hi,
On Sat, Oct 30, 2021 at 10:39:19AM -0400, Rich wrote:
> I see, so "kernel package in oldstable-backports is unusable" is not a bug.
>
> Is there any way I can view why it's been sitting for so long that
> this happened, or any estimate on how much longer it'll be broken?
I did ping yesterday
I see, so "kernel package in oldstable-backports is unusable" is not a bug.
Is there any way I can view why it's been sitting for so long that
this happened, or any estimate on how much longer it'll be broken?
On Wed, Oct 13, 2021 at 10:08:21PM +0200, Salvatore Bonaccorso wrote:
> Hi,
>
> On Mon, Oct 11, 2021 at 10:30:21AM +0200, Christian König wrote:
> > Am 10.10.21 um 16:14 schrieb Xi Ruoyao:
> > > On Sun, 2021-10-10 at 14:46 +0100, Nathaniel Filardo wrote:
> > > > It occurs to me, quite belatedly, t
Processing control commands:
> tags -1 + moreinfo
Bug #804857 [src:linux] linux: New feature: enable CONFIG_NO_HZ_FULL and
CONFIG_RCU_NOCB_CPU/CONFIG_RCU_NOCB_CPU_NONE
Ignoring request to alter tags of bug #804857 to the same tags previously set
--
804857: https://bugs.debian.org/cgi-bin/bugrep
Processing control commands:
> tags -1 + moreinfo
Bug #804857 [src:linux] linux: New feature: enable CONFIG_NO_HZ_FULL and
CONFIG_RCU_NOCB_CPU/CONFIG_RCU_NOCB_CPU_NONE
Added tag(s) moreinfo.
--
804857: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=804857
Debian Bug Tracking System
Contact o
Control: tags -1 + moreinfo
On Wed, Oct 27, 2021 at 10:16:56AM +0200, Georg Müller wrote:
> > But for other configurations it is worse:
> >
> > config NO_HZ_FULL
> > bool "Full dynticks system (tickless)"
> > ...
> > This is implemented at the expense of some overhead in user <->
Processing commands for cont...@bugs.debian.org:
> limit source linux
Limiting to bugs with field 'source' containing at least one of 'linux'
Limit currently set to 'source':'linux'
> tags 994050 + pending
Bug #994050 [src:linux] linux-image-5.10.0-8-amd64: Hauppauge WinTV-HVR1110
DVB-T/Hybrid b
Processing commands for cont...@bugs.debian.org:
> forwarded 994050
> https://lore.kernel.org/linux-media/20210913072649.gb2...@gofer.mess.org/
Bug #994050 [src:linux] linux-image-5.10.0-8-amd64: Hauppauge WinTV-HVR1110
DVB-T/Hybrid bug 125 ms polling on ir-kbd-i2c.ko bad DEFAULT_POLLING_INTERVA
12 matches
Mail list logo
