Hi Felix,
SIGTERM & SIGINT signals received during ubus_complete_request()
waiting for ubus_poll_data() to return are ignored due to
uloop_cancelled being restored to its previous value it had before
uloop_poll_data() was called.
The reproduction scenario is this:
1) cancelled local variable is
Hi Stas,
thanks for the quick reply!
I'm looking for a good way to replace ubiquiti's proprietary TDMA
implementation with something which could be vendor-independent and
interoperable -- and ideally Free Open Source Software.
As TDMA has been implemented for ath9k in FreeBSD, I was wondering if
Hi Alin,
On 2017-02-03 09:29, Alin Năstac wrote:
> Hi Felix,
>
> SIGTERM & SIGINT signals received during ubus_complete_request()
> waiting for ubus_poll_data() to return are ignored due to
> uloop_cancelled being restored to its previous value it had before
> uloop_poll_data() was called.
>
> T
Hi Felix,
The SIGTERM ignore issue I was experiencing before is no longer
reproducible after I apply your patch.
However, I'm concerned about a possible ignore of SIGTERM signal
received during a ubus_complete_request() call. If ctx->stack_depth is
0, any such signal received between prev_uloop_i
On 2017-02-03 15:57, Alin Năstac wrote:
> Hi Felix,
>
> The SIGTERM ignore issue I was experiencing before is no longer
> reproducible after I apply your patch.
>
> However, I'm concerned about a possible ignore of SIGTERM signal
> received during a ubus_complete_request() call. If ctx->stack_dep
On Fri, Feb 3, 2017 at 4:19 PM, Felix Fietkau wrote:
> On 2017-02-03 15:57, Alin Năstac wrote:
>> Hi Felix,
>>
>> The SIGTERM ignore issue I was experiencing before is no longer
>> reproducible after I apply your patch.
>>
>> However, I'm concerned about a possible ignore of SIGTERM signal
>> rece
On 2017-02-03 16:41, Alin Năstac wrote:
> On Fri, Feb 3, 2017 at 4:19 PM, Felix Fietkau wrote:
>> On 2017-02-03 15:57, Alin Năstac wrote:
>>> Hi Felix,
>>>
>>> The SIGTERM ignore issue I was experiencing before is no longer
>>> reproducible after I apply your patch.
>>>
>>> However, I'm concerned
This adds DT bindings for the Cortina systems Gemini SoC
watchdog timer.
Cc: devicet...@vger.kernel.org
Reviewed-by: Guenter Roeck
Acked-by: Rob Herring
Signed-off-by: Linus Walleij
---
ChangeLog v2->v3:
- Fixed spelling error in filename "gemin" to "gemini"
- Collected ACKs
ChangeLog v1->v2:
-
Hi all,
I tried to open the following bug report but Trac's spam filter wouldn't let
me, so I thought I'd raise it on the mailing list to see what you think...
I have a TP-Link TL-MR3020 v1.9 with Chaos Calmer 15.05.01. I'm using it to
provide a WiFi access point to my phone/tablet while I trav
Nick, you can try lede-project bug tracker. I recently released rc1.
Em sex, 3 de fev de 2017 22:18, Nick Malyon escreveu:
> Hi all,
>
> I tried to open the following bug report but Trac's spam filter wouldn't
> let me, so I thought I'd raise it on the mailing list to see what you
> think...
>
>
On 1 February 2017 at 15:29, Jamie Stuart wrote:
> Hello LEDE / OpenWRT devs,
>
> I am requesting your help. First a little background…
...
> This a known issue with the chipset and seems to have been round for years.
> We are currently building on LEDE trunk and still the issue persists.
>
> We a
On 3 February 2017 at 19:17, Nick Malyon wrote:
> If anyone has a workaround that would be great — currently I managed to get
> back in range of a network to make it accessible again, and now I run from
> batteries and delete the wifi client configuration every night before the
> jungle power g
Hey,
I only have my phone, but I have a Terminal app 🙂. Here's the config; I used
the LuCI web interface to manage it. It doesn't seem to make a difference
whether I join the client network then create the AP, or create the AP then
join the network.
In this instance, I joined the network after
13 matches
Mail list logo
