Skip to content

Commit 2b1a9a1

Browse files
bors[bot]mciantyre
andauthored
Merge #119
119: Accept a YAML file, not an SVD file, when patching r=adamgreig a=mciantyre The Rust-based svdtools patch help output suggests that the user provides an SVD file: ``` $ svdtools patch --help svdtools-patch Patches an SVD file as specified by a YAML file USAGE: svdtools patch <SVD_FILE> ARGS: <SVD_FILE> Path to input SVD file OPTIONS: -h, --help Print help information ``` If we actually provide an SVD file, the tool errors. Compare this with the Python documentation, which suggests that the user provides a YAML file, not an SVD file. ``` $ svd patch --help Usage: svd patch [OPTIONS] YAML_FILE Patches an SVD file as specified by a YAML file Options: --help Show this message and exit. ``` Co-authored-by: Ian McIntyre <[email protected]>
2 parents de25a30 + d4331ef commit 2b1a9a1

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

src/cli.rs

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -12,9 +12,9 @@ use svdtools::{
1212
enum Command {
1313
/// Patches an SVD file as specified by a YAML file
1414
Patch {
15-
/// Path to input SVD file
15+
/// Path to input YAML file
1616
#[clap(parse(from_os_str))]
17-
svd_file: PathBuf,
17+
yaml_file: PathBuf,
1818
},
1919
/// Generate Make dependency file listing dependencies for a YAML file.
2020
Makedeps {
@@ -89,7 +89,7 @@ impl Command {
8989
interrupts_cli::parse_device(svd_file, !no_gaps)?;
9090
}
9191
Self::Mmap { svd_file } => mmap_cli::parse_device(svd_file)?,
92-
Self::Patch { svd_file } => patch_cli::patch(svd_file)?,
92+
Self::Patch { yaml_file } => patch_cli::patch(yaml_file)?,
9393
Self::Makedeps {
9494
yaml_file,
9595
deps_file,

0 commit comments

Comments
 (0)