Hei,
On Tue, Aug 20, 2024 at 12:16:00PM +0300, Kalle Valo wrote:
> Moro,
> Riku Voipio writes:
> > I note drivers/net/wireless/ath/ath10k/usb.c comes with the warning:
> >
> > /* TODO: remove this once USB support is fully implemented */
> > ath10k_warn(ar
Hi all,
I note drivers/net/wireless/ath/ath10k/usb.c comes with the warning:
/* TODO: remove this once USB support is fully implemented */
ath10k_warn(ar, "Warning: ath10k USB support is incomplete, don't expect
anything to work!\n");
Is this still the state? If so, Is there alternative
Hi,
I have a problem where rarely, but randomly ModemManager choosest to make
the the connection over the AT rather than the QMI interface. A failed one
looks on the log like:
-snip-
ModemManager (version 1.16.10) starting in system bus...
systemd[1]: Started Modem Manager.
[/dev/cdc-wdm0] Open
Hello All,
The server will stop processing jobs on the 2021-10-15 at around
23:00 UTC, as the server will be put into "Shutdown mode".
The break is to upgrade jenkins and it's plugins as well as the kernel
of the server
Start: 2021-10-16 08:00 UTC
End: 2021-10-16 10:00 UTC
Regards
Riku
Hello All,
The server will stop processing jobs on the 02/07/2021 at around
23:00 UTC, as the server will be put into "Shutdown mode".
The break is to upgrade jenkins and plugins and fix the issue of
jenkins semi-hanging about every two weeks.
Start: 03/07/2021 08:00 UTC
End: 03/07/2021 10:00 UT
Hello All,
The server will stop processing jobs on the 14/05/2021 at around
23:00 UTC, as the server will be put into "Shutdown mode".
We will be going to upgrade the host machine to latest ubuntu LTS,
upgrade jenkins and plugins and make it possible to use LDC cloud
builders
Start: 15/05/2021 0
On Wed, 7 Apr 2021 at 16:13, Riku Voipio wrote:>
> The server will stop processing jobs on the 09/03/2021 at around
> 23:00 UTC, as the server will be put into "Shutdown mode".
> We will be doing the general plugin and LTS update.
> Start: 10/03/2021 08:00 UTC
&g
Hello All,
The server will stop processing jobs on the 09/03/2021 at around
23:00 UTC, as the server will be put into "Shutdown mode".
We will be doing the general plugin and LTS update.
Start: 10/03/2021 08:00 UTC
End: 10/03/2021 10:00 UTC
Regards
__
Hello All,
The server will stop processing jobs on the 29/01/2021 at around
23:00 UTC, as the server will be put into "Shutdown mode".
We will be doing the general plugin and LTS update.
Start: 30/01/2021 08:00 UTC
End: 30/01/2021 10:00 UTC
Regards
__
Hi,
On Wed, Dec 02, 2020 at 09:41:01AM +0100, Vincent Bernat wrote:
> ❦ 1 décembre 2020 22:28 +01, Moritz Mühlenhoff:
> > Michael has been heroically keeping up with this beast of a codebase for
> > years,
> > but we clearly need a broader base to sustain it going forward.
> In the past, it w
Hi,
On Wed, Dec 02, 2020 at 09:41:01AM +0100, Vincent Bernat wrote:
> ❦ 1 décembre 2020 22:28 +01, Moritz Mühlenhoff:
> > Michael has been heroically keeping up with this beast of a codebase for
> > years,
> > but we clearly need a broader base to sustain it going forward.
> In the past, it w
o10+2) buster-backports; urgency=medium
+
+ * Rebuild for buster-backports.
+ * Disable libpmem on arm64. Closes: #971442
+
+ -- Riku Voipio Tue, 17 Nov 2020 14:55:13 +0200
+
qemu (1:5.0-14~bpo10+1) buster-backports; urgency=medium
* Rebuild for buster-backports.
diff --git debian/contr
Hi,
On Mon, 21 Sep 2020 at 12:29, Bastian Germann
wrote:
> Hi Riku,
>
> Thanks, please upload the NMU. As I am not a DD, I do not have commit
> access on the salsa repository. Would you please grant me permission
> (Gitlab user bage)?
Both should be done now,
Riku
On Sun, 20 Sep 2020 at 20:00, Bastian Germann
wrote:
> I would like to salvage the mtd-utils package. The current maintainer is
> unresponsive on the open issues (2014 was the last answer). His last
> main package action was in August 2019, packging the version 2.1.1-1.
> This year, he sponsored a
This should fix it:
https://salsa.debian.org/chromium-team/chromium/-/commit/b904fa41d40b967dcc8f6984db52f7a2f6a2c83d
We are not building with GCC but this seems to be exactly the place where the
crash happens.
chromium built with this patch has not crashed for the last few hours for me,
while
This should fix it:
https://salsa.debian.org/chromium-team/chromium/-/commit/b904fa41d40b967dcc8f6984db52f7a2f6a2c83d
We are not building with GCC but this seems to be exactly the place where the
crash happens.
chromium built with this patch has not crashed for the last few hours for me,
while
Hi all,
The maintenance has been completed.
Regards,
Riku
On Wed, 1 Jul 2020 at 17:24, Riku Voipio wrote:
> Hello All,
>
> The server will stop processing jobs on the 03/07/2020 at around
> 23:00 UTC, as the server will be put into "Shutdown mode".
>
> We will be
forcemerge 964161 964167 964145
thanks
From: Riku Voipio
I haven't been active for a while. Pass the maintainer hat
forward to Laurent, who has done a stellar job filling in.
Signed-off-by: Riku Voipio
---
MAINTAINERS | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git MAINTAINERS MAINTAINERS
index dec25
Hello All,
The server will stop processing jobs on the 03/07/2020 at around
23:00 UTC, as the server will be put into "Shutdown mode".
We will be doing the general plugin and LTS update. This is a major LTS
version upgrade, so the jenkins user interface will come back different
than before.
Star
Hi everyone,
Jenkins is back online. Please open a ticket if you notice any abnormal job
failures.
Regards,
Riku
On Tue, 26 May 2020 at 09:18, Riku Voipio wrote:
> Hi everyone,
>
> Jenkins is down, we are investigating the issue. We'll notify as soon
> jenkins is back up a
Hi everyone,
Jenkins is down, we are investigating the issue. We'll notify as soon
jenkins is back up again.
Regards,
Riku
___
linaro-dev mailing list
linaro-dev@lists.linaro.org
https://lists.linaro.org/mailman/listinfo/linaro-dev
Hello All
ci.linaro.org will stop processing new jobs on the 2019-11-08 at around
22:00 UTC, as the server will be put into "Shutdown mode".
We will be updating plugins and jenkins.
Start: 2019-11-09 07:00 UTC
End: 2019-11-09 10:00 UTC
Regards,
Riku
Hi All,
Jenkins is back building
Riku
On Fri, 4 Oct 2019 at 12:36, Riku Voipio wrote:
>
> Hi All,
>
> Apologies for the short notice, but jenkins needs urgent maintenance.
>
> The server is in now shutdown mode, and should return in a f
Hi All,
Apologies for the short notice, but jenkins needs urgent maintenance.
The server is in now shutdown mode, and should return in a few hours.
Riku
___
linaro-dev mailing list
linaro-dev@lists.linaro.org
https://lists.linaro.org/mailman/listinfo/l
Hello All
ci.linaro.org will stop processing new jobs on the 2019-09-06 at around
22:00 UTC, as the server will be put into "Shutdown mode".
We will be updating plugins and jenkins.
Start: 2019-09-07 08:00 UTC
End: 2019-09-07 11:00 UTC
Regards,
Riku
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Mon, 26 Aug 2019 10:39:56 +0300
Source: mtd-utils
Architecture: source
Version: 1:2.1.1-1
Distribution: unstable
Urgency: medium
Maintainer: Riku Voipio
Changed-By: Riku Voipio
Closes: 902599 921392
Changes:
mtd-utils (1:2.1.1-1
SSH
> > were
> > coming up extremely slow, taking over a minute to start.
> >
> > This is caused by somebody disabling the rng driver for arm64 kernels a
> > long time ago:
> > linux (4.14.13-1) unstable; urgency=medium
> > ...
> > [ Riku Voipio ]
>
SSH
> > were
> > coming up extremely slow, taking over a minute to start.
> >
> > This is caused by somebody disabling the rng driver for arm64 kernels a
> > long time ago:
> > linux (4.14.13-1) unstable; urgency=medium
> > ...
> > [ Riku Voipio ]
>
The build is fixed in:
https://salsa.debian.org/chromium-team/chromium/commits/arm-fixes/debian
I can make an upload if you prefer, or I can wait for you.
Cheers,
Riku
The build is fixed in:
https://salsa.debian.org/chromium-team/chromium/commits/arm-fixes/debian
I can make an upload if you prefer, or I can wait for you.
Cheers,
Riku
On Thu, Jun 06, 2019 at 11:07:31AM +, Riku Voipio wrote:
> Sorry for missign this bug completly. I'll get into fixing at.
I pushed a fix to the arm64 branch:
https://salsa.debian.org/chromium-team/chromium/commit/945283642d205c7b5a5129030f525109ee7b22c1
Riku
On Thu, Jun 06, 2019 at 11:07:31AM +, Riku Voipio wrote:
> Sorry for missign this bug completly. I'll get into fixing at.
I pushed a fix to the arm64 branch:
https://salsa.debian.org/chromium-team/chromium/commit/945283642d205c7b5a5129030f525109ee7b22c1
Riku
Hi,
Sorry for missign this bug completly. I'll get into fixing at.
Riku
Hi,
Sorry for missign this bug completly. I'll get into fixing at.
Riku
Hi, All,
On Mon, 3 Jun 2019 at 11:30, Riku Voipio wrote:
> Hi All,
>
> Apologies for the short notice, but jenkins needs to be restarted today.
>
> The server is in shutdown mode, and the jenkins process will be restarted
> at
>
> 2019-06-03 09.00 - 10.00 UTC
>
>
Hi All,
Apologies for the short notice, but jenkins needs to be restarted today.
The server is in shutdown mode, and the jenkins process will be restarted at
2019-06-03 09.00 - 10.00 UTC
Riku
___
linaro-dev mailing list
linaro-dev@lists.linaro.org
htt
Hi Jonas,
Please go for it! I'm never offended if people fix bugs in my packages :)
Riku
On Sun, 31 Mar 2019 at 13:51, Jonas Smedegaard wrote:
> Dear Riku,
>
> Are you still interested in maintaining the package u-boot-menu?
>
> I notice that your last upload was 1.5 years ago, and you have no
Hello All,
obs.linaro.org will be moved over to a new machine. We don't expect any
interruption, but some builds may end up having to be re-triggered after
the move. Time window for handover:
Start: 2019-03-11 07:00 UTC
End: 2019-03-11 08:00 UTC
___
li
Hello All,
The server will stop processing jobs on the 2019-02-22 at around
22:00 UTC, as the server will be put into "Shutdown mode".
We will be updating docker, Jenkins and the builders.
Start: 2019-02-23 07:00 UTC
End: 2019-02-23 10:00 UTC
Regards
___
Maintainer: Debian Chromium Team
Changed-By: Riku Voipio
Description:
chromium - web browser
chromium-common - web browser - common resources used by the chromium packages
chromium-driver - web browser - WebDriver support
chromium-l10n - web browser - language packs
chromium-sandbox - web
Maintainer: Debian Chromium Team
Changed-By: Riku Voipio
Description:
chromium - web browser
chromium-common - web browser - common resources used by the chromium packages
chromium-driver - web browser - WebDriver support
chromium-l10n - web browser - language packs
chromium-sandbox - web
Maintainer: Debian Chromium Team
Changed-By: Riku Voipio
Description:
chromium - web browser
chromium-common - web browser - common resources used by the chromium packages
chromium-driver - web browser - WebDriver support
chromium-l10n - web browser - language packs
chromium-sandbox - web
From: Riku Voipio
bison/flex is now needed always for building for kconfig. Some build
dependencies depend on kernel configuration, enable them as needed:
- libelf-dev when UNWINDER_ORC is set
- libssl-dev for SYSTEM_TRUSTED_KEYRING
Since the libssl-dev is needed for extract_cert binary
From: Riku Voipio
bison/flex is now needed always for building since genksyms is always
generated. Some build dependencies depend on kernel configuration,
enable them as needed:
- libelf-dev when UNWINDER_ORC is set
- libssl-dev for SYSTEM_TRUSTED_KEYRING
Since the libssl-dev is needed for
On Mon, Nov 26, 2018 at 12:37:57PM +0100, Raphael Hertzog wrote:
> were in the week-end). I was aware of the discussion but did not
> had the time to chime in, yet I was the person who re-opened the bug
> #881333 in the first place.
> I also invited someone else who is working on a concrete proje
On Mon, Nov 26, 2018 at 12:37:57PM +0100, Raphael Hertzog wrote:
> were in the week-end). I was aware of the discussion but did not
> had the time to chime in, yet I was the person who re-opened the bug
> #881333 in the first place.
> I also invited someone else who is working on a concrete proje
On Mon, Nov 26, 2018 at 12:37:57PM +0100, Raphael Hertzog wrote:
> were in the week-end). I was aware of the discussion but did not
> had the time to chime in, yet I was the person who re-opened the bug
> #881333 in the first place.
> I also invited someone else who is working on a concrete proje
On Mon, Nov 26, 2018 at 12:37:57PM +0100, Raphael Hertzog wrote:
> were in the week-end). I was aware of the discussion but did not
> had the time to chime in, yet I was the person who re-opened the bug
> #881333 in the first place.
> I also invited someone else who is working on a concrete proje
On Mon, Nov 26, 2018 at 12:37:57PM +0100, Raphael Hertzog wrote:
> were in the week-end). I was aware of the discussion but did not
> had the time to chime in, yet I was the person who re-opened the bug
> #881333 in the first place.
> I also invited someone else who is working on a concrete proje
On Thu, Nov 22, 2018 at 07:14:44PM -0300, Lisandro Damián Nicanor Pérez Meyer
wrote:
> El jueves, 22 de noviembre de 2018 18:30:39 -03 Marcin Juszkiewicz escribió:
> > Does it mean that arm64 box with PCI Express graphics card will be not
> > able to use Qt based software? I can put Radeon or NVid
On Thu, Nov 22, 2018 at 07:14:44PM -0300, Lisandro Damián Nicanor Pérez Meyer
wrote:
> El jueves, 22 de noviembre de 2018 18:30:39 -03 Marcin Juszkiewicz escribió:
> > Does it mean that arm64 box with PCI Express graphics card will be not
> > able to use Qt based software? I can put Radeon or NVid
On Thu, Nov 22, 2018 at 07:14:44PM -0300, Lisandro Damián Nicanor Pérez Meyer
wrote:
> El jueves, 22 de noviembre de 2018 18:30:39 -03 Marcin Juszkiewicz escribió:
> > Does it mean that arm64 box with PCI Express graphics card will be not
> > able to use Qt based software? I can put Radeon or NVid
Hi everyone,
Maintenance moved by one week, time now:
Start: 2018-11-17 09:00 UTC
End: 2018-11-17 12:00 UTC
Riku
On Mon, 5 Nov 2018 at 15:43, Riku Voipio wrote:
>
> Hello All,
>
> The server will stop processing jobs on the 2018-11-09 at around
> 19:00 UTC, as the server w
Hello All,
The server will stop processing jobs on the 2018-11-09 at around
19:00 UTC, as the server will be put into "Shutdown mode".
We will be updating plugins, Jenkins and the docker builders.
Start: 2018-11-10 09:00 UTC
End: 2018-11-10 12:00 UTC
Regards
___
On Tue, Sep 04, 2018 at 11:43:07AM -0700, Geoff Levand wrote:
> > Is it resolved? Graeme Gregory claimed
> > (https://www.spinics.net/lists/arm-kernel/msg669946.html) that "most
> > people are running the firmware provided from HPe support but was never
> > put on release site".
>
> I took that as
On Tue, Sep 04, 2018 at 11:43:07AM -0700, Geoff Levand wrote:
> > Is it resolved? Graeme Gregory claimed
> > (https://www.spinics.net/lists/arm-kernel/msg669946.html) that "most
> > people are running the firmware provided from HPe support but was never
> > put on release site".
>
> I took that as
On Thu, Aug 02, 2018 at 11:53:04PM +, Riku Voipio wrote:
> The issue seems to be binutils in stable not supporting LR = x30 alias. I've
> built a fixed version. I'm travelling now, but once I get back, I'll test the
> fix and submit patch upstream. Similar issue for
On Thu, Aug 02, 2018 at 11:53:04PM +, Riku Voipio wrote:
> The issue seems to be binutils in stable not supporting LR = x30 alias. I've
> built a fixed version. I'm travelling now, but once I get back, I'll test the
> fix and submit patch upstream. Similar issue for
On Thu, Jun 14, 2018 at 09:58:56AM +0100, Ian Campbell wrote:
> On Wed, 2018-06-13 at 12:25 -0700, Geoff Levand wrote:
> > On 06/09/2018 05:15 AM, Ian Campbell wrote:
> >
> > > I think this is probably something for the arch (or perhaps
> > > platform)
> > > code to deal with. See for example all
On Thu, Jun 14, 2018 at 09:58:56AM +0100, Ian Campbell wrote:
> On Wed, 2018-06-13 at 12:25 -0700, Geoff Levand wrote:
> > On 06/09/2018 05:15 AM, Ian Campbell wrote:
> >
> > > I think this is probably something for the arch (or perhaps
> > > platform)
> > > code to deal with. See for example all
tags 904796 + patch upstream
thanks
On Mon, Jul 30, 2018 at 01:37:57AM +, Riku Voipio wrote:
> On Sat, Jul 28, 2018 at 05:23:14PM -0400, Michael Gilbert wrote:
> > > Chromium on arm64 in Debian Stretch stopped receiving security updates.
> > > Chromium for i386, amd
tags 904796 + patch upstream
thanks
On Mon, Jul 30, 2018 at 01:37:57AM +, Riku Voipio wrote:
> On Sat, Jul 28, 2018 at 05:23:14PM -0400, Michael Gilbert wrote:
> > > Chromium on arm64 in Debian Stretch stopped receiving security updates.
> > > Chromium for i386, amd
On Sat, Jul 28, 2018 at 05:23:14PM -0400, Michael Gilbert wrote:
> > Chromium on arm64 in Debian Stretch stopped receiving security updates.
> > Chromium for i386, amd64 and armhf received updates for versions 67 and
> > 68, however chromium for arm64 is stuck on version 66.
> There was a build e
On Sat, Jul 28, 2018 at 05:23:14PM -0400, Michael Gilbert wrote:
> > Chromium on arm64 in Debian Stretch stopped receiving security updates.
> > Chromium for i386, amd64 and armhf received updates for versions 67 and
> > 68, however chromium for arm64 is stuck on version 66.
> There was a build e
On Thu, Jun 28, 2018 at 08:11:14PM +0200, Florian Weimer wrote:
> * Niels Thykier:
>
> > armel/armhf:
> >
> >
> > * Undesirable to keep the hardware running beyond 2020. armhf VM
> >support uncertain. (DSA)
> >- Source: [DSA Sprint report]
>
> Fedora is facing an issue runn
On Thu, Jun 28, 2018 at 08:11:14PM +0200, Florian Weimer wrote:
> * Niels Thykier:
>
> > armel/armhf:
> >
> >
> > * Undesirable to keep the hardware running beyond 2020. armhf VM
> >support uncertain. (DSA)
> >- Source: [DSA Sprint report]
>
> Fedora is facing an issue runn
On Thu, Jun 28, 2018 at 08:11:14PM +0200, Florian Weimer wrote:
> * Niels Thykier:
>
> > armel/armhf:
> >
> >
> > * Undesirable to keep the hardware running beyond 2020. armhf VM
> >support uncertain. (DSA)
> >- Source: [DSA Sprint report]
>
> Fedora is facing an issue runn
On Thu, Jun 28, 2018 at 08:11:14PM +0200, Florian Weimer wrote:
> * Niels Thykier:
>
> > armel/armhf:
> >
> >
> > * Undesirable to keep the hardware running beyond 2020. armhf VM
> >support uncertain. (DSA)
> >- Source: [DSA Sprint report]
>
> Fedora is facing an issue runn
On Thu, Jun 28, 2018 at 08:11:14PM +0200, Florian Weimer wrote:
> * Niels Thykier:
>
> > armel/armhf:
> >
> >
> > * Undesirable to keep the hardware running beyond 2020. armhf VM
> >support uncertain. (DSA)
> >- Source: [DSA Sprint report]
>
> Fedora is facing an issue runn
On Thu, Jun 28, 2018 at 08:11:14PM +0200, Florian Weimer wrote:
> * Niels Thykier:
>
> > armel/armhf:
> >
> >
> > * Undesirable to keep the hardware running beyond 2020. armhf VM
> >support uncertain. (DSA)
> >- Source: [DSA Sprint report]
>
> Fedora is facing an issue runn
On Thu, Jun 28, 2018 at 08:11:14PM +0200, Florian Weimer wrote:
> * Niels Thykier:
>
> > armel/armhf:
> >
> >
> > * Undesirable to keep the hardware running beyond 2020. armhf VM
> >support uncertain. (DSA)
> >- Source: [DSA Sprint report]
>
> Fedora is facing an issue runn
On Thu, Jun 28, 2018 at 08:11:14PM +0200, Florian Weimer wrote:
> * Niels Thykier:
>
> > armel/armhf:
> >
> >
> > * Undesirable to keep the hardware running beyond 2020. armhf VM
> >support uncertain. (DSA)
> >- Source: [DSA Sprint report]
>
> Fedora is facing an issue runn
On Thu, Jun 28, 2018 at 08:11:14PM +0200, Florian Weimer wrote:
> * Niels Thykier:
>
> > armel/armhf:
> >
> >
> > * Undesirable to keep the hardware running beyond 2020. armhf VM
> >support uncertain. (DSA)
> >- Source: [DSA Sprint report]
>
> Fedora is facing an issue runn
On Thu, Jun 28, 2018 at 08:11:14PM +0200, Florian Weimer wrote:
> * Niels Thykier:
>
> > armel/armhf:
> >
> >
> > * Undesirable to keep the hardware running beyond 2020. armhf VM
> >support uncertain. (DSA)
> >- Source: [DSA Sprint report]
>
> Fedora is facing an issue runn
On Thu, Jun 28, 2018 at 08:11:14PM +0200, Florian Weimer wrote:
> * Niels Thykier:
>
> > armel/armhf:
> >
> >
> > * Undesirable to keep the hardware running beyond 2020. armhf VM
> >support uncertain. (DSA)
> >- Source: [DSA Sprint report]
>
> Fedora is facing an issue runn
On Thu, Jun 28, 2018 at 08:11:14PM +0200, Florian Weimer wrote:
> * Niels Thykier:
>
> > armel/armhf:
> >
> >
> > * Undesirable to keep the hardware running beyond 2020. armhf VM
> >support uncertain. (DSA)
> >- Source: [DSA Sprint report]
>
> Fedora is facing an issue runn
reassign 901290 gcc-6
notfound 901290 68.0.3440.7-1
found 6.4.0-17
thanks
Compiling chrome 68 with results an gcc ICE. This affects both arm64[1] and
armhf[2]. Filing against gcc-6 as this what buildd used, but this affects
other versions too:
+---+---+---+---+
| | gcc-6 |
reassign 901290 gcc-6
notfound 901290 68.0.3440.7-1
found 6.4.0-17
thanks
Compiling chrome 68 with results an gcc ICE. This affects both arm64[1] and
armhf[2]. Filing against gcc-6 as this what buildd used, but this affects
other versions too:
+---+---+---+---+
| | gcc-6 |
reassign 901290 gcc-6
notfound 901290 68.0.3440.7-1
found 6.4.0-17
thanks
Compiling chrome 68 with results an gcc ICE. This affects both arm64[1] and
armhf[2]. Filing against gcc-6 as this what buildd used, but this affects
other versions too:
+---+---+---+---+
| | gcc-6 |
Verified this affects gcc6, gcc7 and gcc8. I'll file a bug against GCC once I
get a reduced testcase.
Compile with clang6 works.
Riku
Verified this affects gcc6, gcc7 and gcc8. I'll file a bug against GCC once I
get a reduced testcase.
Compile with clang6 works.
Riku
Maintainer: Debian Chromium Team
Changed-By: Riku Voipio
Description:
chromium - web browser
chromium-common - web browser - common resources used by the chromium packages
chromium-driver - web browser - WebDriver support
chromium-l10n - web browser - language packs
chromium-shell - web
; options)
> added an arm64 specific CONFIG_ACPI_NFIT=y, overriding the default of =m, but
> the
> commit message mentions nothing about why this was done.
>
> Remove the arm64 specific setting and use the default of module build.
>
> Cc: Riku Voipio
> Signed-off-by: Geoff Lev
; options)
> added an arm64 specific CONFIG_ACPI_NFIT=y, overriding the default of =m, but
> the
> commit message mentions nothing about why this was done.
>
> Remove the arm64 specific setting and use the default of module build.
>
> Cc: Riku Voipio
> Signed-off-by: Geoff Lev
From: Riku Voipio
Reading doc/README.distro , we see platform needs to set
pxefile_addr_r to support distro boot.
Signed-off-by: Riku Voipio
---
include/configs/stih410-b2260.h | 1 +
1 file changed, 1 insertion(+)
diff --git a/include/configs/stih410-b2260.h b/include/configs/stih410-b2260
On 7 May 2018 at 16:35, Masahiro Yamada wrote:
> Hi Riku,
>
> 2018-05-07 16:11 GMT+09:00 :
>> From: Riku Voipio
>>
>> There is multiple issues with the genaration of maintainer string
>>
>> It uses DEBEMAIL and EMAIL enviroment variables, which may
From: Riku Voipio
There is multiple issues with the genaration of maintainer string
It uses DEBEMAIL and EMAIL enviroment variables, which may contain angle
brackets,
creating invalid maintainer strings. The documented KBUILD_BUILD_USER and
KBUILD_BUILD_HOST variables are not used
From: Riku Voipio
There is multiple issues with the genaration of maintainer string
It uses DEBEMAIL and EMAIL enviroment variables, which may contain angle
brackets,
creating invalid maintainer strings. The documented KBUILD_BUILD_USER and
KBUILD_BUILD_HOST variables are not used
On 23 April 2018 at 22:50, Mathieu Malaterre wrote:
> Be nice to the user and check env vars KBUILD_BUILD_USER &
> KBUILD_BUILD_HOST when those are set.
mkdebian sets the maintainer address as "$name <$email>", but this
patch only sets the email part. I also wonder about the precedence, I
think K
reassign 564935 ftp.debian.org
retitle 564935 gmod -- RoM; ancient; abandoned upstream;
thanks
On Mon, Apr 16, 2018 at 07:19:36PM +0200, Moritz Muehlenhoff wrote:
> On Tue, Jan 12, 2010 at 09:08:39PM +, Simon McVittie wrote:
> > Source: gmod
> > Severity: wishlist
> > User: debian...@lists.deb
tags +876774 pending
thanks
On Wed, Apr 04, 2018 at 07:08:01PM +0200, Josua Mayer wrote:
> Greetings once again,
>
> I have now rebuilt the current kernel package from sid, with the
> necessary config changes.
> So far it boots, and network works. I haven't tested anything else yet.
>
> Please f
tags +876774 pending
thanks
On Wed, Apr 04, 2018 at 07:08:01PM +0200, Josua Mayer wrote:
> Greetings once again,
>
> I have now rebuilt the current kernel package from sid, with the
> necessary config changes.
> So far it boots, and network works. I haven't tested anything else yet.
>
> Please f
From: Riku Voipio
Move debian/ directory generation out of builddeb to a new script,
mkdebian. The package build commands are kept in builddeb, which
is now an internal command called from debian/rules.
With these changes in place, we can now use dpkg-buildpackage from
deb-pkg and bindeb-pkg
On 29 March 2018 at 03:20, Ben Hutchings wrote:
> On Wed, 2018-03-28 at 11:58 +0300, Riku Voipio wrote:
> [...]
>> One option:
>>
>> +++ b/scripts/package/mkdebian
>> cat < debian/rules
>> -#!/usr/bin/make -f
>> #!$(which $MAKE) -f
> [..]
>
>
On Tue, Mar 27, 2018 at 01:52:46PM -0700, Vagrant Cascadian wrote:
> On 2018-03-27, Riku Voipio wrote:
> > I've created a merge request to add Dragonboard 820c support
> > in debian u-boot build:
> >
> > https://salsa.debian.org/debian/u-boot/merge_requests/1
>
On 27 March 2018 at 18:23, Masahiro Yamada
wrote:
> Riku,
>
> 2018-03-27 22:28 GMT+09:00 Riku Voipio :
>
>>> If I use GNU Make 4.2
>>>
>>> $ cat deb_pkg_log.txt
>>> MAKEFLAGS for deb-pkg: rR -I/home/masahiro/ref/linux -j8
>>> --jobse
resend, sorry forgot the mailing lists from last post.
Hi Masahiro,
On 27 March 2018 at 12:07, Masahiro Yamada
wrote:
> 2018-02-21 19:10 GMT+09:00 :
>> From: Riku Voipio
>>
>> Move debian/ directory generation out of builddeb to a new script,
>> mkdebian. The pack
Package: u-boot-qcom
Version: 2018.03+dfsg1-1
Severity: wishlist
Tags: patch
Hi,
I've created a merge request to add Dragonboard 820c support
in debian u-boot build:
https://salsa.debian.org/debian/u-boot/merge_requests/1
Riku
On 21 March 2018 at 07:15, Jan Kiszka wrote:
> Since d5d332d3f7e8, a couple of links in scripts/dtc/include-prefixes
> are additionally required in order to build device trees with the header
> package.
A bit odd usecase IMHO, but:
Reviewed-by: Riku Voipio
> Signed-off-by
1 - 100 of 4686 matches
Mail list logo
