It's broken for ARMv5, which is the only armeb target in OpenWrt.
Signed-off-by: Rosen Penev
---
package/libs/nettle/Makefile | 7 ++-
1 file changed, 6 insertions(+), 1 deletion(-)
diff --git a/package/libs/nettle/Makefile b/package/libs/nettle/Makefile
index 62c39702ed..b9324e4793 100644
Hi Adrian,
On 2019-12-27 21:07, m...@adrianschmutzler.de wrote:
thanks for your work, but for the reasons I wrote earlier I do not
think this should be backported.
Just for reference: I assume you are referencing to
https://github.com/openwrt/openwrt/pull/2574#issuecomment-559460188,
which
Hi,
can anyone cherry-pick b81cee86e63d4421072839ec8a3780d8afff9337 to 19.07
?
Thanks, Sven
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Hi Sven,
> -Original Message-
> From: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org]
> On Behalf Of Sven Roederer
> Sent: Freitag, 13. Dezember 2019 20:51
> To: openwrt-devel@lists.openwrt.org
> Cc: Luochongjun
> Subject: [OpenWrt-Devel] [PATCH 19.07] ath79: add support fo
Hi,
> -Original Message-
> From: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org]
> On Behalf Of Matthias Schiffer
> Sent: Montag, 16. Dezember 2019 21:25
> To: Adrian Schmutzler
> Cc: openwrt-devel@lists.openwrt.org
> Subject: Re: [OpenWrt-Devel] [PATCH] ramips: fix port se
Hi again,
> -define Device/dir-860l-b1
> +define Device/dlink_dir-860l-b1
This would break sysupgrade, as SUPPORTED_DEVICES is derived from device
definition name, and thus would change.
So, this shouldn't be applied if someone really plans to do it.
BTW That's a good example of why backporting
Hi,
> >> Master had this updated a while ago, it's okay there.
> >
> >Though I'm a big fan of unification and made an effort to have this
> >sorted out in master, I do not think backporting those device name
> >changes is very helpful. This will create additional work, but
> >effectively it will j
On Sat, Dec 21, 2019 at 2:32 AM Gerard Ryan wrote:
>
> Does anyone have any tips on how to expedite the review of this patch?
> Am I missing something or is the patch malformed?
Patch looks fine; some style comments inline
Hans
>
> Thanks in advance,
> Gerard
>
> On Tue, Oct 22, 2019 at 7:08 PM G
Petr Štetiar kirjoitti 27.12.2019 klo 16.15:
In commit 5d7ca8309d0a ("ubusd/libubus-io: fix variable sized struct
position warning") the position of cmsghdr struct has been changed in
order to fix clang-9 compiler warning, but it has introduced regression
in at least `logread` which hanged indefi
As announced on the mailing list, WireGuard will be in Linux 5.6. As a
result, the wg(8) tool, used by OpenWRT in the same manner as ip(8), is
moving to its own wireguard-tools repo. Meanwhile, the out-of-tree
kernel module for kernels 3.10 - 5.5 moved to its own wireguard-linux-
compat repo. Yeste
In commit 5d7ca8309d0a ("ubusd/libubus-io: fix variable sized struct
position warning") the position of cmsghdr struct has been changed in
order to fix clang-9 compiler warning, but it has introduced regression
in at least `logread` which hanged indefinitely.
So this patch reworks the socket descr
Petr Štetiar [2019-12-27 13:25:41]:
> Hannu Nyman [2019-12-27 11:33:46]:
>
> > Hopefully you/somebody will revert the ubus changes in master until then.
>
> can you confirm, that following fix[1] actually fixes the issues you're
> seeing? Thanks.
This should be hopefully proper fix https://pa
In commit 5d7ca8309d0a ("ubusd/libubus-io: fix variable sized struct
position warning") the position of cmsghdr struct has been changed in
order to fix clang-9 compiler warning, but it has introduced regression
in at least `logread` which hanged indefinitely.
So this patch reworks the socket descr
On Fri, 27 Dec 2019 at 16:53, Rafał Miłecki wrote:
>
> From: Rafał Miłecki
>
> This reverts commit 32c3126b2f0464106d74317336b6aef1d7d5f82f.
>
> Internal list of devices guarantees some basic sorting (by device type
> and then a name) but nothing more. In particular it's not guaranteed
> (and it'
Hannu Nyman [2019-12-27 11:33:46]:
Hi,
> Hopefully you/somebody will revert the ubus changes in master until then.
can you confirm, that following fix[1] actually fixes the issues you're
seeing? Thanks.
1.
https://gitlab.com/ynezz/openwrt-ubus/commit/184d756c70a3dd2cf5b21d0d5672f08091832cc1
From: Rafał Miłecki
Devices handled with autofs should be seen as available even if
currently unmounted. Mounting is handled on demand and transparently for
users.
Signed-off-by: Rafał Miłecki
---
blockd.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/blockd.c b/blockd.c
index e07530c.
Petr Štetiar kirjoitti 27.12.2019 klo 0.59:
Hannu Nyman [2019-12-26 22:37:31]:
Hi,
I noticed today problems with new master builds, both with ipq806x/R7800 and
ar71xx/WNDR3700:
* Some services do not start and their processes are not visible in the
process list. Examples: collectd and nlbwmo
From: Rafał Miłecki
This reverts commit 32c3126b2f0464106d74317336b6aef1d7d5f82f.
Internal list of devices guarantees some basic sorting (by device type
and then a name) but nothing more. In particular it's not guaranteed
(and it's actually quite uncommon) that all preceding entries are parent
d
18 matches
Mail list logo
