> The clean code, without my downstream patch is already here
> https://github.com/openwrt/openwrt/commit/f24c47fa8a2fb653288d34e7a0bcdc6eafa5736e
> . I'll still test it on my device before submitting.
PR: https://github.com/openwrt/openwrt/pull/17654
It does not include the vlan/forwarding extra
Hi Linus,
> > Maybe we should back port the upstream changes (and fixes),
> > similar to what I did in
> > https://github.com/luizluca/openwrt/commit/d145c6845d7cdd2d49722a85988f16b17014dfa4
> > (it needs to be updated and rebased). I might have time to rebase that
> > branch soon.
>
> What about
On Wed, 15 Jan 2025 at 14:56, Cyril Brulebois wrote:
>
> Hi Luca,
>
> Luca Boccassi (2025-01-15):
> > I plan to split out udev-udeb and libudev1-udeb from the current
> > src:systemd source package/repo into a new src:systemd-udeb (forked
> > from the old one, so ge
> > The upstream was rearranged in such a way that reverses the relation
> > between subdrivers and interfaces. It will probably break your
> > packages.
>
> Indeed. It was a bit annoying...
>
> We are falling behind mainline again.
>
> > Maybe we should back port the upstream changes (and fixes),
root@noble:/tmp/libdnf-0.69.0# dpkg -c
../python3-libdnf_0.69.0-2.3build3_amd64.deb | grep _module
-rw-r--r-- root/root904272 2024-03-31 02:54
./usr/lib/python3/dist-packages/libdnf/_module.cpython-312-x86_64-linux-gnu.so
--
You received this bug notification because you are a member of Ub
Yes a workaround in libdnf is possible, in fact I had added one before
dh-python was fixed:
https://salsa.debian.org/pkg-rpm-
team/libdnf/-/commit/02de151278a0831d1c5c4c7d47c4a4f46766c666
I have just tested adding the same snippet to d/rules in a Noble chroot,
and rebuilt the package, and the pro
root@noble:/tmp/libdnf-0.69.0# dpkg -c
../python3-libdnf_0.69.0-2.3build3_amd64.deb | grep _module
-rw-r--r-- root/root904272 2024-03-31 02:54
./usr/lib/python3/dist-packages/libdnf/_module.cpython-312-x86_64-linux-gnu.so
--
You received this bug notification because you are a member of Ub
Yes a workaround in libdnf is possible, in fact I had added one before
dh-python was fixed:
https://salsa.debian.org/pkg-rpm-
team/libdnf/-/commit/02de151278a0831d1c5c4c7d47c4a4f46766c666
I have just tested adding the same snippet to d/rules in a Noble chroot,
and rebuilt the package, and the pro
** Bug watch added: Debian Bug tracker #1068255
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068255
** Also affects: dh-python (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068255
Importance: Unknown
Status: Unknown
--
You received this bug notification be
** Bug watch added: Debian Bug tracker #1068255
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068255
** Also affects: dh-python (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068255
Importance: Unknown
Status: Unknown
--
You received this bug notification be
Public bug reported:
dh-python in Noble, on architectures other than amd64, renames libdnf
binary modules and breaks them:
I: dh_python3 fs:418: renaming _module.so to
_.cpython-312-aarch64-linux-gnu.so
https://launchpadlibrarian.net/722671993/buildlog_ubuntu-noble-
arm64.libdnf_0.69.0-2.3build3
Public bug reported:
dh-python in Noble, on architectures other than amd64, renames libdnf
binary modules and breaks them:
I: dh_python3 fs:418: renaming _module.so to
_.cpython-312-aarch64-linux-gnu.so
https://launchpadlibrarian.net/722671993/buildlog_ubuntu-noble-
arm64.libdnf_0.69.0-2.3build3
Reviewed-by: Luca Vizzarro
Hello Dmitry, Maxime, All,
On Fri, 10 Jan 2025 11:58:19 +0100
Luca Ceresoli wrote:
> Hi Dmitry,
>
> On Thu, 2 Jan 2025 13:01:49 +0100
> Luca Ceresoli wrote:
>
> > > > diff --git a/drivers/gpu/drm/bridge/samsung-dsim.c
> > > > b/drivers/gpu/
On Wed, 15 Jan 2025 at 23:12, Sven Geuer wrote:
>
> On Wed, 2025-01-15 at 20:28 +0100, Thorsten Glaser wrote:
> > On Wed, 15 Jan 2025, Sven Geuer wrote:
> >
> > > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=504044#162
> >
> > > Applying ExecCondition to me seems the most reasonable solutio
On Wed, 15 Jan 2025 at 23:12, Sven Geuer wrote:
>
> On Wed, 2025-01-15 at 20:28 +0100, Thorsten Glaser wrote:
> > On Wed, 15 Jan 2025, Sven Geuer wrote:
> >
> > > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=504044#162
> >
> > > Applying ExecCondition to me seems the most reasonable solutio
On Sun, 12 Jan 2025 02:22:07 +0100 (CET) Thorsten Glaser
wrote:
> On Sat, 26 Oct 2024, Sven Geuer wrote:
>
> >Feel free to integrate my additions into your repo. You might want
to
> >test the sysv-init functionality still works. According to my tests
> >sysv-init and systemd unit work flawlessly
On Wed, 15 Jan 2025 at 23:12, Sven Geuer wrote:
>
> On Wed, 2025-01-15 at 20:28 +0100, Thorsten Glaser wrote:
> > On Wed, 15 Jan 2025, Sven Geuer wrote:
> >
> > > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=504044#162
> >
> > > Applying ExecCondition to me seems the most reasonable solutio
In my experience SRUs tend to get stonewalled and end up going nowhere,
backports are much easier and actually end up happening. It's entirely
fine for our use case for this to be in backports, so I'm ok with this.
--
You received this bug notification because you are a member of Ubuntu
Backporte
In my experience SRUs tend to get stonewalled and end up going nowhere,
backports are much easier and actually end up happening. It's entirely
fine for our use case for this to be in backports, so I'm ok with this.
--
You received this bug notification because you are a member of Ubuntu
Bugs, whi
lgtm. thanks!
Reviewed-by: Luca Vizzarro
On 15/01/2025 15:41, Dean Marx wrote:
Also, I noticed after submitting this first version that suites where
some cases are skipped and the rest pass have a 100% pass rate in the
results report. Should this also mean that suites where every case is
skipped have a 100% pass rate? Right now this rep
Alright scratch that then. The only thing I'd change Dean is the name of
the method. Saying testsuite is somewhat redundant, I think just log fine.
This has now been reworked and superseded by series-34355.
ves 'vdevs' from 'system_under_test_node' and moves
it into 'test_runs'.
Bugzilla ID: 1360
Signed-off-by: Nicholas Pratte
Signed-off-by: Luca Vizzarro
Reviewed-by: Paul Szczepanek
---
dts/conf.yaml| 20 +-
dts/framework/c
From: Nicholas Pratte
The build options configuration contained redundant fields that were not
in use, and there is no future scope for their use.
Bugzilla ID: 1360
Signed-off-by: Nicholas Pratte
Signed-off-by: Luca Vizzarro
Reviewed-by: Paul Szczepanek
---
dts/conf.yaml
them.
Bugzilla ID: 1344
Signed-off-by: Nicholas Pratte
Signed-off-by: Luca Vizzarro
Reviewed-by: Paul Szczepanek
---
doc/guides/tools/dts.rst | 78 ++-
dts/.gitignore| 4 +
dts/conf.yaml | 84 ---
dts
uites if none are specified.
Bugzilla ID: 1360
Signed-off-by: Luca Vizzarro
Reviewed-by: Paul Szczepanek
---
dts/framework/config/test_run.py | 16 +++-
1 file changed, 15 insertions(+), 1 deletion(-)
diff --git a/dts/framework/config/test_run.py b/dts/framework/config/test_run.py
1598
Signed-off-by: Nicholas Pratte
Signed-off-by: Luca Vizzarro
Reviewed-by: Paul Szczepanek
---
dts/framework/config/__init__.py | 40
dts/framework/runner.py | 18 +++---
2 files changed, 39 insertions(+), 19 deletions(-)
diff --git
From: Nicholas Pratte
The 'arch' attribute in the conf.yaml is unnecessary, as this can be
readily discovered directly from any given node.
Bugzilla ID: 1360
Signed-off-by: Nicholas Pratte
Signed-off-by: Luca Vizzarro
Reviewed-by: Paul Szczepanek
---
dts
From: Nicholas Pratte
To further the simplification of the user configuration, use_first_core
can be inferred from the lcores. If the user explicitly includes the
core 0 in the lcores range, it will only then be used.
Bugzilla ID: 1360
Signed-off-by: Nicholas Pratte
Signed-off-by: Luca
- prefixed the template configuration files with example
allowing users to place their own configuration files
where the defaults would stay. Also added these to
.gitignore
Best,
Luca
Luca Vizzarro (3):
dts: handle CLI overrides in the configuration
dts: split configuration file
dts
-2~bpo24.04.1) noble-backports;
urgency=medium
- * Rebuild for noble-backports. (LP: #)
+ * Rebuild for noble-backports. (LP: #2095011)
- -- Luca Boccassi Wed, 15 Jan 2025 13:12:59 +0000
+ -- Luca Boccassi Wed, 15 Jan 2025 13:12:59 +
--
You received this bug notification beca
** Attachment added: "sphinxcontrib-globalsubs_0.1.2-2~bpo24.04.1.dsc"
https://bugs.launchpad.net/ubuntu/+source/sphinxcontrib-globalsubs/+bug/2095011/+attachment/5851903/+files/sphinxcontrib-globalsubs_0.1.2-2~bpo24.04.1.dsc
--
You received this bug notification because you are a member of U
** Attachment added:
"sphinxcontrib-globalsubs_0.1.2-2~bpo24.04.1_source.buildinfo"
https://bugs.launchpad.net/ubuntu/+source/sphinxcontrib-globalsubs/+bug/2095011/+attachment/5851902/+files/sphinxcontrib-globalsubs_0.1.2-2~bpo24.04.1_source.buildinfo
--
You received this bug notification be
** Attachment added:
"sphinxcontrib-globalsubs_0.1.2-2~bpo24.04.1_source.changes"
https://bugs.launchpad.net/ubuntu/+source/sphinxcontrib-globalsubs/+bug/2095011/+attachment/5851901/+files/sphinxcontrib-globalsubs_0.1.2-2~bpo24.04.1_source.changes
--
You received this bug notification becaus
** Attachment added: "debdiff"
https://bugs.launchpad.net/ubuntu/+source/sphinxcontrib-globalsubs/+bug/2095011/+attachment/5851900/+files/debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/20950
a dch --bpo
changelog entry with the appropriate version, such as:
sphinxcontrib-globalsubs (0.1.2-2~bpo24.04.1) noble-backports;
urgency=medium
* Rebuild for noble-backports. (LP: #2095011)
-- Luca Boccassi Wed, 15 Jan 2025 13:12:59 +
** Affects: sphinxcontrib-globalsubs (Ubuntu
Hi Cyril,
I plan to split out udev-udeb and libudev1-udeb from the current
src:systemd source package/repo into a new src:systemd-udeb (forked
from the old one, so generated udebs will be the same).
This should greatly reduce your workload as src:systemd uploads will
no longer be in your way and
Sorry for the late reply Dean. This is a bit redundant in my opinion,
there is no reason not to give full access to the test suite's own
logger. I'd just change TestSuite._logger into TestSuite.logger to
indicate that it's a public member, and do what you initially did.
Looks good.
Reviewed-by: Luca Vizzarro
Hi Dean,
good timing! I actually noticed this issue last week and was going to
tackle it soon.
On 13/01/2025 21:52, Dean Marx wrote:
@@ -324,13 +324,15 @@ def generate_pass_rate_dict(self, test_run_summary) ->
dict[str, float]:
Returns:
A dictionary with the PASS/FAI
https://bugs.kde.org/show_bug.cgi?id=498540
--- Comment #4 from Luca Saalfeld ---
Created attachment 177352
--> https://bugs.kde.org/attachment.cgi?id=177352&action=edit
Left cut off link, right correct link
I'm not sure if we both are talking about different things.
In the sc
Hi Linus,
Em dom., 12 de jan. de 2025, 20:15, Linus Walleij
escreveu:
>
> This adds kernel packages for the Realtek RTL836x switches.
>
> My intended usage is for RTL8366RB, but let's package
> RTL8365MB while we are at it. I did not create separate
> packages for the two switches, as it complic
Package: rng-tools-debian
Version: 2.5
Severity: grave
Dear Maintainers,
Thanks for adding a native systemd service!
I noticed that in an autopkgtest-build-qemu VM the service fails:
root@host:~# systemctl status --no-pager -l rng-tools-debian
× rng-tools-debian.service - Hardware RNG entropy g
Package: rng-tools-debian
Version: 2.5
Severity: grave
Dear Maintainers,
Thanks for adding a native systemd service!
I noticed that in an autopkgtest-build-qemu VM the service fails:
root@host:~# systemctl status --no-pager -l rng-tools-debian
× rng-tools-debian.service - Hardware RNG entropy g
Moreover, installing an hook is cluster-wide, right? Is there a way to
limit an hook only for connections related to a single database
(without taking into account FDW and friends)?
Thanks,
Luca
tly only DMC wakelock handling) are called.
>
> v2:
> - Move functions to intel_display_irq.c instead of having them in
>intel_de.h. (Jani)
>
> Cc: Jani Nikula
> Signed-off-by: Gustavo Sousa
> ---
LGTM.
Reviewed-by: Luca Coelho
--
Cheers,
Luca.
https://bugs.kde.org/show_bug.cgi?id=498540
--- Comment #2 from Luca Saalfeld ---
I just compiled the git master to see this too and I got it again (though in
this case it just says 'Link to ').
The commands I've used:
mkdir \#TestFolder
touch \#TestFolder/TestFile
ln -s \#Test
Alcuni passaggi mi paiono parecchio interessanti, ad esempio in tema di
educazione.
https://www.vatican.va/content/francesco/it/speeches/2025/january/documents/20250109-corpo-diplomatico.html
Buona lettura
dl
_
don Luca Peyron
Pastorale Universitaria - Apostolato
Package: iipimage-server
Version: 1.1-3+b2
Severity: normal
Tags: upstream
Dear Maintainer,
the new 1.2 release of the iipimage-server has been missing for years and it'd
be great if it could be included in the packaging system. See also #1053404.
-- System Information:
Debian Release: 12.9
A
Package: iipimage-server
Version: 1.1-3+b2
Severity: normal
Tags: upstream
Dear Maintainer,
the new 1.2 release of the iipimage-server has been missing for years and it'd
be great if it could be included in the packaging system. See also #1053404.
-- System Information:
Debian Release: 12.9
A
On Wed, 8 Jan 2025 at 23:08, Daniel Kahn Gillmor wrote:
>
> Thanks for this discussion, all--
>
> On Tue 2025-01-07 15:16:27 +0100, Simon Josefsson wrote:
> > I believe this would be good, I frequently run into GnuPG bugs in the
> > 2.2.x branch that was fixed years ago in 2.4
>
> Can you identify
On Sun, 12 Jan 2025 20:12:58 +0100 1...@gmx.us wrote:
> Hi,
>
> I have been following this bug for a while now. I tried just
installing the packages systemd-boot-efi and systemd-boot-efi-amd64-
signed, without removing grub-efi-amd64 and grub-efi-amd64-signed.
Machine was still booting with grub.
On Sun, 12 Jan 2025 20:12:58 +0100 1...@gmx.us wrote:
> Hi,
>
> I have been following this bug for a while now. I tried just
installing the packages systemd-boot-efi and systemd-boot-efi-amd64-
signed, without removing grub-efi-amd64 and grub-efi-amd64-signed.
Machine was still booting with grub.
Control: tags -1 wontfix
Control: close -1
On Sun, 26 May 2024 18:15:12 +0100 Luca Boccassi
wrote:
> Control: tags -1 help
>
> On Sat, 09 Dec 2023 23:53:17 +0100 Matteo Settenvini
> wrote:
> > Package: systemd-boot
> > Version: 255-1
> > Severity: impo
Control: tags -1 wontfix
Control: close -1
On Sun, 26 May 2024 18:15:12 +0100 Luca Boccassi
wrote:
> Control: tags -1 help
>
> On Sat, 09 Dec 2023 23:53:17 +0100 Matteo Settenvini
> wrote:
> > Package: systemd-boot
> > Version: 255-1
> > Severity: impo
commit: c2a94e8b649bfcf08de4ac796e2c7ff27bd7de0a
Author: Luca Barbato gentoo org>
AuthorDate: Sun Jan 12 08:07:53 2025 +
Commit: Luca Barbato gentoo org>
CommitDate: Sun Jan 12 09:03:45 2025 +
URL:https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=c2a94e8
of years. It is not the 1980s anymore, and the uid range does
not stop at 65k. This is documented in detail at
https://systemd.io/UIDS-GIDS/ Yes, this is not how "things used to
work", and that's ok, stuff can change.
Thanks.
On Sat, 11 Jan 2025 at 19:19, Niels Thykier wrote:
>
&
https://bugs.kde.org/show_bug.cgi?id=498540
Luca Saalfeld changed:
What|Removed |Added
CC||lulukl...@gmail.com
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=498540
Bug ID: 498540
Summary: Symlinks with '#' in their path are cut off
Classification: Applications
Product: dolphin
Version: 24.12.1
Platform: Arch Linux
OS: Linux
Statu
Reviewed-by: Luca Vizzarro
Reviewed-by: Luca Vizzarro
Reviewed-by: Luca Vizzarro
Reviewed-by: Luca Vizzarro
Hi Dmitry,
On Thu, 2 Jan 2025 13:01:49 +0100
Luca Ceresoli wrote:
> > > diff --git a/drivers/gpu/drm/bridge/samsung-dsim.c
> > > b/drivers/gpu/drm/bridge/samsung-dsim.c
> > > index
> > > f8b4fb8357659018ec0db65374ee5d05330639ae..c4d1563fd32019efde
Reviewed-by: Luca Vizzarro
Source: dracut
Version: 105-3
User: debian...@lists.debian.org
Usertags: flaky
Severity: grave
Justification: blocks other packages from migrating
Dear Maintainer(s),
The new upstream-dracut-network-nfs autopkgtest fails on amd64,
blocking other packages from migrating to test when they get sched
Source: dracut
Version: 105-3
User: debian...@lists.debian.org
Usertags: flaky
Severity: grave
Justification: blocks other packages from migrating
Dear Maintainer(s),
The new upstream-dracut-network-nfs autopkgtest fails on amd64,
blocking other packages from migrating to test when they get sched
the possibility to read what was discussed also to those
who couldn’t attend it.
If you want, you are invited to share this invitation with all the
people you think might be interested in this call.
We hope to see you and/or read you very soon!
Luca/Sannita
[1]
https://commons.wikimedia.org/
14593e3995a ("xen/device-tree: Allow region overlapping with
/memreserve/ ranges")
Signed-off-by: Luca Fancellu
Reviewed-by: Michal Orzel
---
Changes from v2:
- Banks created by Xen should be MEMORY type. (Michal)
- Add R-by Michal
Changes from v1:
- Changed commit title and body msg
Control: tags -1 -moreinfo
Control: tags -1 unreproducible
Control: close -1
On Thu, 9 Jan 2025 at 12:12, Norbert Lange wrote:
>
> Am Do., 9. Jan. 2025 um 12:11 Uhr schrieb Luca Boccassi :
> >
> > Control: tags -1 moreinfo
> >
> > On Thu, 09 Jan 2025 10:51:41
Control: tags -1 -moreinfo
Control: tags -1 unreproducible
Control: close -1
On Thu, 9 Jan 2025 at 12:12, Norbert Lange wrote:
>
> Am Do., 9. Jan. 2025 um 12:11 Uhr schrieb Luca Boccassi :
> >
> > Control: tags -1 moreinfo
> >
> > On Thu, 09 Jan 2025 10:51:41
On Thu, 9 Jan 2025 at 11:32, Michael Biebl wrote:
>
> On Tue, 07 Jan 2025 15:38:11 +0000 Luca Boccassi wrote:
> > Source: upower
> > Version: 0.8.0
> > User: debian...@lists.debian.org
> > Usertags: flaky
> > Severity: grave
> > Justification: blocks
Source: debusine
Version: 0.8.0
User: debian...@lists.debian.org
Usertags: flaky
Severity: grave
Justification: blocks other packages from migrating
Dear Maintainer(s),
debusine autopkgtest are flaky and fail most of the runs on s390x:
https://ci.debian.net/packages/d/debusine/testing/s390x/
Th
On Thu, 9 Jan 2025 at 11:32, Michael Biebl wrote:
>
> On Tue, 07 Jan 2025 15:38:11 +0000 Luca Boccassi wrote:
> > Source: upower
> > Version: 0.8.0
> > User: debian...@lists.debian.org
> > Usertags: flaky
> > Severity: grave
> > Justification: blocks
On Thu, 9 Jan 2025 at 11:32, Michael Biebl wrote:
>
> On Tue, 07 Jan 2025 15:38:11 +0000 Luca Boccassi wrote:
> > Source: upower
> > Version: 0.8.0
> > User: debian...@lists.debian.org
> > Usertags: flaky
> > Severity: grave
> > Justification: blocks
Source: debusine
Version: 0.8.0
User: debian...@lists.debian.org
Usertags: flaky
Severity: grave
Justification: blocks other packages from migrating
Dear Maintainer(s),
debusine autopkgtest are flaky and fail most of the runs on s390x:
https://ci.debian.net/packages/d/debusine/testing/s390x/
Th
Control: tags -1 moreinfo
On Thu, 09 Jan 2025 10:51:41 +0100 Norbert Lange
wrote:
> Package: systemd-boot
> Version: 257.1-7
> Severity: important
> X-Debbugs-Cc: nolang...@gmail.com
>
> Dear Maintainer,
>
> I am running a fresh installation form the debian testing installer,
> while installing
Control: tags -1 moreinfo
On Thu, 09 Jan 2025 10:51:41 +0100 Norbert Lange
wrote:
> Package: systemd-boot
> Version: 257.1-7
> Severity: important
> X-Debbugs-Cc: nolang...@gmail.com
>
> Dear Maintainer,
>
> I am running a fresh installation form the debian testing installer,
> while installing
_type?
> At first I was expecting gnttab to be MEMORY as well. I don't see a
> difference between a region prepared by Xen
> for domain to store gnttab vs extended regions. Both specify regions of
> unused address space. It's just that the region
> for gnttab must always be present but extended regions don't have to.
Right, at first I thought gnttab could be reserved memory, but now that you
pointed out it’s not the right thing to do, I remember
now that these type reflects the device tree grouping for the memory banks, so
RESERVED_MEMORY is only for these regions
in the /reserved-memory tree, STATIC_SHARED_MEMORY is for the
'xen,domain-shared-memory-v1’ comaptible node and
MEMORY is for /memory regions.
Now I would say that we could use MEMORY also for regions prepared by Xen as
long as we don’t need to differentiate them in
a different way from /memory regions.
Please let me know your thoughts.
Cheers,
Luca
Hi Michal,
> On 9 Jan 2025, at 10:00, Michal Orzel wrote:
>
> Hi Luca,
>
> Is this patch for 4.20? I would say so, therefore it should have "for-4.20"
> tag and Oleksii as release manager
> should be CCed. Doing it now.
Thanks, I forgot the procedure
&
14593e3995a ("xen/device-tree: Allow region overlapping with
/memreserve/ ranges")
Signed-off-by: Luca Fancellu
---
Changes from v1:
- Changed commit title and body msg
- initialised max_banks and type for all structures using 'struct membanks_hdr'
I didn't get why the fixe
quot;, GUC_UNIT_S is what I was looking for.
Luca
Il 08/01/25 22:58, Diego Nieto Cid ha scritto:
On Wed, Jan 08, 2025 at 10:25:41AM +0100, Luca wrote:
Il 08/01/25 02:30, dnie...@gmail.com ha scritto:
+
+static char * features_edx[] =
+ {
+"fpu", "vme", "de", "pse", "tsc", "msr",
Package: molly-guard
Version: 0.8.4
Dear Maintainer(s),
molly-guard currently works by diverting an arbitrary series of legacy
executables to avoid accidental reboots. While this worked in ye olde
times when executables where the only way to reboot a system, those
days are long past.
There are s
t; > > > Hi,
> > > >
> > > > Most of these comments affect your earlier patches, but let's work on
> > > > the API-level view.
> > > >
> > > > On Tue, Dec 31, 2024 at 11:39:58AM +0100, Luca Ceresoli wrote:
>
>
gt; the API-level view.
> >
> > On Tue, Dec 31, 2024 at 11:39:58AM +0100, Luca Ceresoli wrote:
> > > + * When using refcounted mode, the driver should allocate ``struct
> > > + * my_bridge`` using regular allocation (as opposed to ``devm_`` or
> > > + * `
On Wed, 8 Jan 2025 at 14:35, Peter Pentchev wrote:
>
> On Wed, Jan 08, 2025 at 10:19:34AM +0100, Julien Plissonneau Duquène wrote:
> > Le 2025-01-07 21:52, Peter Pentchev a écrit :
> > >
> > > Hm. That sounds interesting, but I think the Debian project cannot
> > > protect such a mirror from autom
Control: tags -1 wontfix
Control: close -1
On Wed, 08 Jan 2025 17:07:29 +0800 WHR wrote:
> Package: systemd
> Version: 252.26-1~deb12u2
> Severity: wishlist
> X-Debbugs-Cc: w...@rivoreo.one
>
> When system has a SSH service open to the internet, it is very common
that
> this service attracting a
Control: tags -1 wontfix
Control: close -1
On Wed, 08 Jan 2025 17:07:29 +0800 WHR wrote:
> Package: systemd
> Version: 252.26-1~deb12u2
> Severity: wishlist
> X-Debbugs-Cc: w...@rivoreo.one
>
> When system has a SSH service open to the internet, it is very common
that
> this service attracting a
.
Any suggestion is appreciated.
Thanks,
Luca
del_name + 10 * sizeof(unsigned int), (char *) &ecx,
sizeof(unsigned int));
+ memcpy(model_name + 11 * sizeof(unsigned int), (char *) &edx,
sizeof(unsigned int));
+}
+
+ fprintf(m,
+"processor : 0\n"
+"vendor_id : %s\n"
+"cpu family : %d\n"
+"model : %d\n"
+"model name : %s\n"
+"stepping: %d\n",
+vendor, family, model, model_name, stepping);
+
+ fprintf(m, "flags :");
+ for (index = 0; index < 32; index++)
+{
+ if (features_edx[index] == NULL)
+continue;
+ if (feature_edx & (1 << index))
+fprintf(m, " %s", features_edx[index]);
+}
+ for (index = 0; index < 32; index++)
+{
+ if (features_ecx[index] == NULL)
+continue;
+ if (feature_ecx & (1 << index))
+fprintf(m, " %s", features_ecx[index]);
+}
+
+ fprintf(m, "\n\n");
+
+out:
+ fclose(m);
+ return err;
+}
maybe this can be already made arch-specific.
Luca
> On 8 Jan 2025, at 09:01, Luca Fancellu wrote:
>
>
>
>> On 8 Jan 2025, at 07:57, Michal Orzel wrote:
>>
>> In the original patch e7a80636f16e ("xen/arm: add cache coloring support
>> for Xen image"), the stub was added under wrong assumption
mption is
> incorrect as we already rely on DCE for cases like this one. Therefore
> drop the stub, that otherwise would be a place potentially prone to
> errors in the future.
>
> Suggested-by: Julien Grall
> Signed-off-by: Michal Orzel
> ---
Reviewed-by: Luca Fancellu
Reviewed-by: Luca Vizzarro
Source: upower
Version: 0.8.0
User: debian...@lists.debian.org
Usertags: flaky
Severity: grave
Justification: blocks other packages from migrating
Dear Maintainer(s),
debusine autopkgtest are flaky and fail most of the runs on s390x:
https://ci.debian.net/packages/d/debusine/testing/s390x/
This
Source: upower
Version: 0.8.0
User: debian...@lists.debian.org
Usertags: flaky
Severity: grave
Justification: blocks other packages from migrating
Dear Maintainer(s),
debusine autopkgtest are flaky and fail most of the runs on s390x:
https://ci.debian.net/packages/d/debusine/testing/s390x/
This
Source: upower
Version: 0.8.0
User: debian...@lists.debian.org
Usertags: flaky
Severity: grave
Justification: blocks other packages from migrating
Dear Maintainer(s),
debusine autopkgtest are flaky and fail most of the runs on s390x:
https://ci.debian.net/packages/d/debusine/testing/s390x/
This
: add MTU config methods to testpmd shell")
Signed-off-by: Luca Vizzarro
Reviewed-by: Paul Szczepanek
---
Hi there,
sending a fix discovered after running pmd_buffer_scatter on Mellanox.
Which should just skip, but the capability checks fail.
Best,
Luca
---
dts/framework/remo
1 - 100 of 3859 matches
Mail list logo
