Skip to content
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.

Sign up for GitHub

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

Jump to bottom

[mio] Introduce mio-tflite12121 #11432

Merged
merged 1 commit into from
Sep 1, 2023
Merged

[mio] Introduce mio-tflite12121 #11432

merged 1 commit into from
Sep 1, 2023

Conversation

seanshpark
Copy link
Contributor

This will introduce mio-tflite1212 for tflite version 2.12.1.

ONE-DCO-1.0-Signed-off-by: SaeHie Park [email protected]

@seanshpark
[mio] Introduce mio-tflite12121
29b0fb0 
This will introduce mio-tflite1212 for tflite version 2.12.1.

ONE-DCO-1.0-Signed-off-by: SaeHie Park <[email protected]>
@seanshpark
Copy link
Contributor Author

for #11390 , from #11387

jinevening
jinevening approved these changes Sep 1, 2023
View reviewed changes
Copy link
Contributor

@jinevening jinevening left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

nit) the title may need to be changed 12121 -> 2121.

We may need to introduce a separator ex: 2121 -> 2.12.1

@seanshpark
Copy link
Contributor Author

nit) the title may need to be changed 12121 -> 2121.

thanks! I'll update this when landing

We may need to introduce a separator ex: 2121 -> 2.12.1

This was cause existing ones had 260 or 280 ... -_-;;;;

@seanshpark seanshpark merged commit b0cfbe0 into Samsung:master Sep 1, 2023
3 checks passed
@seanshpark seanshpark deleted the mio_tflite2121 branch September 1, 2023 04:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@jinevening jinevening jinevening approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@seanshpark @jinevening