Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks @mazzy89 - I left some comments
@devimc makes complete sense. I will make the changes |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks @mazzy89 - I left some comments
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks @mazzy89
@jodh-intel please take a look |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @mazzy89.
A couple of comments.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @mazzy89.
lgtm
@jodh-intel thank you for the fast reaction in picking up this and the nice PR flow. |
np. Thanks very much for your contribution @mazzy89! Before this lands, please could you squash the commits into a single one please? |
Np. a pleasure. thank you for this neat and useful library. |
Signed-off-by: Salvatore Mazzarino <dev@mazzarino.cz>
All green - thanks again @mazzy89! |
@jodh-intel I've noticed that adding the logger to fwcfg now causes the error to be printed out always when fwcfg is empty because the validation func runs always. Is something that we want? |
@mazzy89 - I think this is a problem. And in fact looking at the
If you agree, do you want to raise a follow-on PR for this? |
I have a PR already to fix another issue. So I'm going to modify this in here #150 |
Thanks @mazzy89. |
Signed-off-by: Salvatore Mazzarino dev@mazzarino.cz
Append
fw_cfg
flag