Re: [PATCH] firmware: hardcode the debug message for -ENOENT

2019-02-19 Thread Luis Chamberlain
On Sun, Feb 17, 2019 at 04:25:10PM +0800, yuank...@codeaurora.org wrote: > On 2019-02-05 07:30 AM, Luis Chamberlain wrote: > > On Mon, Jan 14, 2019 at 05:58:30PM +0800, yuank...@codeaurora.org wrote: > > > Hi, > > > > > > Refined at below. > > > > > > From bbd0d9c8f28eb78ca34353347c3d4092e88f

Re: [PATCH] firmware: hardcode the debug message for -ENOENT

2019-02-17 Thread yuankuiz
On 2019-02-05 07:30 AM, Luis Chamberlain wrote: On Mon, Jan 14, 2019 at 05:58:30PM +0800, yuank...@codeaurora.org wrote: Hi, Refined at below. From bbd0d9c8f28eb78ca34353347c3d4092e88f000c Mon Sep 17 00:00:00 2001 This is all garbled, not sure why your patch looks all messed up. Are you

Re: [PATCH] firmware: hardcode the debug message for -ENOENT

2019-02-04 Thread Luis Chamberlain
On Mon, Jan 14, 2019 at 05:58:30PM +0800, yuank...@codeaurora.org wrote: > Hi, > > Refined at below. > > From bbd0d9c8f28eb78ca34353347c3d4092e88f000c Mon Sep 17 00:00:00 2001 This is all garbled, not sure why your patch looks all messed up. Are you using git sendemail or something manual?

Re: [PATCH] firmware: hardcode the debug message for -ENOENT

2019-01-14 Thread yuankuiz
Hi, Refined at below. From bbd0d9c8f28eb78ca34353347c3d4092e88f000c Mon Sep 17 00:00:00 2001 When the return code of "-ENOENT" was printed inside of the debug message, which could be hardcoded meaningfully. Signed-off-by: John Zhao --- drivers/base/firmware_loader/main.c | 8 1