-
Notifications
You must be signed in to change notification settings - Fork 337
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
target/riscv: new ebreak
controls
#1168
Conversation
6b1faa6
to
ccb13a1
Compare
@JanMatCodasip, @MarekVCodasip ping |
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.
Overall the change looks all right - thank you.
I have finished my review and do not expect to have any further 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.
Thank you for addressing the suggestions so far.
I have noticed three more items, and shouldn't have more comments than that.
Please, note: In the last change I didn't only address review 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.
LGTM, thank you.
* Deprecate `riscv set_ebreak*` commands. * Introduce RISC-V-sepecific `configure` parameter `-ebreak` instead. * Separate controls for VS and VU modes. Change-Id: I0ff88318dcb52af6923eb9f20f9d0c056ad09cf0 Signed-off-by: Evgeniy Naydanov <[email protected]>
@JanMatCodasip, can you please double-check and re-approve the patch. I'd like to merge it. |
@en-sc If I read the changes since the last review correctly, this patch has only been rebased (without further changes). Is that correct? If so, it LGTM :) |
riscv set_ebreak*
commands.configure
parameter-ebreak
instead.Change-Id: I0ff88318dcb52af6923eb9f20f9d0c056ad09cf0