On 11/12/2019 15:22, Daniel Golle wrote:
As a community, we decided to give our self a set of minimal rules[1].
And even though it is in the last position, rule #12 "Be nice to each
other." is meant just as serious as all the other rules.
So here, not for the first time, you are using languag
Yep, that does the trick. Thank you!
Tested-by: Martin Weinelt
On 12/14/19 11:38 PM, David Bauer wrote:
With this patch, txpower for the PHY is applied when configuring the PHY
instead of the VIF. Otherwise, the configured txpower is not applied for
the first initialized VIF when using DFS cha
With this patch, txpower for the PHY is applied when configuring the PHY
instead of the VIF. Otherwise, the configured txpower is not applied for
the first initialized VIF when using DFS channels, as it is currently
applied to early when the CAC hasn't finished.
Reported-by: Martin Weinelt
---
.
On Sun, Nov 17, 2019 at 01:42:04PM -0800, Rosen Penev wrote:
> Several CMake packages such as log4cplus and protobuf(-c) install to
> lib64 instead of lib on some hosts. This completely breaks rpath linking.
> Override it globally to avoid fixing each package individually.
>
> Signed-off-by: Rosen
From: Rafał Miłecki
This fixes problem with corrupting data buffer by a subsequent data
read. This was originally reported in the:
libblkid-tiny: bugged buffer management
Message-ID: <94e6f04d-19c5-3818-0748-db4ec0d48...@gmail.com>
Please verify I didn't add any memory leak. I hope I actually fi
From: Rafał Miłecki
This allows reading multiple chunks of block device data and operating
on them simultaneously. Previous implementation was using a single
buffer (except for reading more data than allocated size) and subsequent
reads were corrupting memory of previously returned buffers.
This
From: Rafał Miłecki
This adds blkid_new_probe() and blkid_free_probe() which have to be used
in place of simple struct memory allocation. They will allow extending
probe struct by any extra initialization code and resources release.
Newly introduced probe.c file is based on original libblkid's c
This enables the system LED to indicate a running firmware upgrade. This
pattern is used on most platforms provided by the generic base-files
package. ar71xx uses it's own implementation for the system-LED, where
the upgrade case is not yet implemented.
Signed-off-by: David Bauer
---
target/linu
On Sat, Dec 14, 2019 at 02:12:55PM +0300, Paul Fertser wrote:
> Should a uci-defaults script be added to base-files that would
> populate the system config with all the LEDs present in the DT but not
> added by board config?
cd /sys/class/leds
for i in *; do
uci show system | grep -q sysf
Hello,
Some follow-up thoughts, could someone clarify please?
On Sat, Dec 14, 2019 at 02:10:28AM +0300, Paul Fertser wrote:
> On Fri, Dec 13, 2019 at 11:51:14PM +0100, Sven Roederer wrote:
> > good point. But also on master seems to be no entry for this board in
> > "01_leds". So I assume the de
10 matches
Mail list logo
