-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Extend kconfig #93
Extend kconfig #93
Conversation
Big miss in our test configuration... Signed-off-by: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Again yet another miss in our compilation test coverage. Signed-off-by: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
…efconfig DYNAMIC_DEBUG is really a requirement for all SOF uses, that's how we detect issues with sof-test scripts. The rest is more for developers. Signed-off-by: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
This split allows for codecs to be selected only on the basis of machine drivers selected, or conversely to be all included for developers. kconfig-sof-default-nodev.sh now includes only the bare minimum for SOF. Signed-off-by: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
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.
Can you add the new script/subset to the README.md?
Also, to be on the safe side please at least one run of daily tests between merging this PR and the previous one.
A bit of a lost cause but since there is a brand new .sh file it wouldn't hurt to make it shellcheck clean.
Off-topic: most .sh have basically the same boilerplate code + just a list of defconfigs. In the future it could be nice to have a more generic.sh script that can read new *-deconfig.list files instead. It would make custom subsets easier. No big deal.
The README is 3 years old, it should be redone in a separate PR. The tests were done already with the initial version. I don't know how to make shell scripts pretty/better. I don't have any knowledge on what is legal/dangerous/simpler... |
Shellcheck often does it for you. In this case just missing a lot of quotes (typical) |
or just cryptic errors
|
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.
Since you're testing LNL, could you also add CONFIG_DRM_XE?
PS: thanks for the shellcheck fixes. I was only suggesting them for the new .sh file, now it's drowing the Kconfig changes... separate, concurrent PR?
@@ -1,20 +1,21 @@ | |||
#!/bin/bash |
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.
I think this file is only meant to be sourced, not invoked directory so I wouldn't do this.
shellcheck is like checkpatch: it's right most of the time but all the time.
There are ways to silence specific warnings but since shellcheck is not run in CI in this repo then I wouldn't bother.
kconfig-lib.sh
Outdated
|
||
BUILD_DIR=$(pwd) | ||
|
||
# find merge_config in code directory | ||
FILE=scripts/kconfig/merge_config.sh | ||
if test -f "$FILE"; then | ||
COMMAND=$FILE; | ||
export COMMAND=$FILE; |
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.
Again I believe this file is meant to be sourced so I don't think this export
makes sense.
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.
if I don't use export shellcheck complains that the variable is not used.
In kconfig-lib.sh line 18:
COMMAND=$SOURCE_DIR/$FILE;
^-----^ SC2034 (warning): COMMAND appears unused. Verify use (or export if used externally).
what the heck.
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.
Ideally shellcheck would analyze this file only indirectly when sourced from another file - exactly like how it's being used.
In practice just ignore this warning.
Yes following shell "includes" is a bit painful with shellcheck, you need |
started device tests
|
used double-quotes and export tested with: "shellcheck kconfig-*.sh" Signed-off-by: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
1923c68
to
abd21d3
Compare
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.
Looks good but I'm not familiar with these + the README.md is 3 years old.
Still no CONFIG_DRM_XE?
EDIT: just noticed yesterday's commit 3b1d9da
follow-up to PR #92 with additions this time.