On 2017-02-16 02:19, Andy Shevchenko wrote:
On Thu, Feb 16, 2017 at 12:29 AM, Rafał Miłecki
wrote:
From: Rafał Miłecki
This isn't critical as we use platform NVRAM as fallback and it's very
common case of all Broadcom home routers. Thanks for the new
On 2017-02-16 02:19, Andy Shevchenko wrote:
On Thu, Feb 16, 2017 at 12:29 AM, Rafał Miłecki
wrote:
From: Rafał Miłecki
This isn't critical as we use platform NVRAM as fallback and it's very
common case of all Broadcom home routers. Thanks for the new firmware
loading function we can achieve
On Thu, Feb 16, 2017 at 12:29 AM, Rafał Miłecki wrote:
> From: Rafał Miłecki
>
> This isn't critical as we use platform NVRAM as fallback and it's very
> common case of all Broadcom home routers. Thanks for the new firmware
> loading function we can achieve
On Thu, Feb 16, 2017 at 12:29 AM, Rafał Miłecki wrote:
> From: Rafał Miłecki
>
> This isn't critical as we use platform NVRAM as fallback and it's very
> common case of all Broadcom home routers. Thanks for the new firmware
> loading function we can achieve this by simply passing FW_OPT_NO_WARN.
From: Rafał Miłecki
This isn't critical as we use platform NVRAM as fallback and it's very
common case of all Broadcom home routers. Thanks for the new firmware
loading function we can achieve this by simply passing FW_OPT_NO_WARN.
Signed-off-by: Rafał Miłecki
From: Rafał Miłecki
This isn't critical as we use platform NVRAM as fallback and it's very
common case of all Broadcom home routers. Thanks for the new firmware
loading function we can achieve this by simply passing FW_OPT_NO_WARN.
Signed-off-by: Rafał Miłecki
---
Kalle, Arend: this patch is
6 matches
Mail list logo