On 7/27/21 9:50 AM, Josef Schlehofer wrote:
On 24. 07. 21 20:03, Hauke Mehrtens wrote:
On 7/24/21 7:50 PM, Josef Schlehofer wrote:
On 24. 07. 21 19:37, Hauke Mehrtens wrote:
On 7/1/21 11:08 AM, Robert Marko wrote:
On Thu, Jul 1, 2021 at 12:42 AM Marek Behun
wrote:
On Wed, 30 Jun 2021
Based on the discussion on the mailing list [1], the patch which was
reverted, it reverts only one patch without the subsequent ones.
This leads to the SoC scaling issue not using a CPU parent clock, but
it uses DDR clock. This is done for all variants, and it's wrong because
commits (hacks) that
This patch is backported from linux-arm-kernel [1] to improve situation, when
it was reported that 1.2 GHz variant is unstable with DFS.
It waits to be accepted upstream, however, it waits for Marvell people to
respond.
[1]
On 24. 07. 21 20:03, Hauke Mehrtens wrote:
> On 7/24/21 7:50 PM, Josef Schlehofer wrote:
>>
>> On 24. 07. 21 19:37, Hauke Mehrtens wrote:
>>> On 7/1/21 11:08 AM, Robert Marko wrote:
On Thu, Jul 1, 2021 at 12:42 AM Marek Behun
wrote:
>
> On Wed, 30 Jun 2021 17:51:24 +0200
>
This patch is backported from linux-arm-kernel [1] to improve situation, when
it was reported that 1.2 GHz variant is unstable with DFS.
It waits to be accepted upstream, however, it waits for Marvell people to
respond.
[1]
Based on the discussion on the mailing list [1], the patch which was
reverted, it reverts only one patch without the subsequent ones.
This leads to the SoC scaling issue not using a CPU parent clock, but
it uses DDR clock. This is done for all variants, and it's wrong because
commits (hacks) that
When streaming the syslog messages via udp, the socket connection always
succeeds by definition, but it can still fail to send. In such case,
the syslog keep repeating the following two messages:
failed to send log data to ip:port via udp
Logread connected to ip:port
With this change,
Fixes: 41664054b8b1 ("logd: fix ignored return values in set{gid,uid}")
Signed-off-by: Giovanni Giacobbi
---
log/logd.c | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/log/logd.c b/log/logd.c
index 5d6c458..594b1e0 100644
--- a/log/logd.c
+++ b/log/logd.c
@@ -243,37
As I learn more about DSA, I want to make two requests to help out people who
support OpenWrt on the forums.
For the next several years, a question of the form, "I just upgraded my router
from X to Y, and the networking stopped working...", will mean we have to
figure out if this could be a
On 27/07/2021 14:39, Giovanni Giacobbi wrote:
Fixes: 41664054b8b1 ("logd: fix ignored return values in set{gid,uid}")
Signed-off-by: Giovanni Giacobbi
---
log/logd.c | 8
1 file changed, 4 insertions(+), 4 deletions(-)
Let me add some remarks about this change. Comments on each
If the "logread" process is blocked in write call or stopped by
pressing "CTRL+Z", the logd starts to buffer all the messages in
the write buffer. Since currently there is no limit in ustream
w.max_buffers, the logd consumes all the system memory and at a
point of time which triggers Out Of
If the "logread" process is blocked in write call or stopped by
pressing "CTRL+Z", the logd starts to buffer all the messages in
the write buffer. Since currently there is no limit in ustream
w.max_buffers, the logd consumes all the system memory and at a
point of time which triggers Out Of
Add the missing CONFIG_KCSAN (disabled). Found while making kernel_oldconfig on
an x86-64 subtarget.
Signed-off-by: Rui Salvaterra
---
target/linux/generic/config-5.10 | 1 +
1 file changed, 1 insertion(+)
diff --git a/target/linux/generic/config-5.10 b/target/linux/generic/config-5.10
index
13 matches
Mail list logo
