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.

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

tock-registers: Next release to crates.io? #2138

Closed
andre-richter opened this issue Oct 4, 2020 · 2 comments · Fixed by #2191
Closed

tock-registers: Next release to crates.io? #2138

andre-richter opened this issue Oct 4, 2020 · 2 comments · Fixed by #2191
Labels
release-blocker Issue or PR that must be resolved before the next release

Comments

@andre-richter
Copy link
Contributor

Hi all, @ppannuto,

I see that tock-registers got a fair share of changes since the 0.5.0 release. Especially the switch to UnsafeCell looks important.

Can you we make a new release to crates.io, or are there any gating issues?

Thanks,
Andre

@ppannuto
Copy link
Member

ppannuto commented Oct 5, 2020

No gating issues.. just hasn't hit the top of the priority queue here :/

We're very near a feature freeze for Tock 1.6 release. The release testing should more thoroughly cover all of the register changes -- not that we've seen any problems yet. Let's take advantage of that, and I'll plan on kicking out a tock-registers release contemporaneously with Tock 1.6 [likely timeline >1 week, <1 month].

@ppannuto ppannuto added the release-blocker Issue or PR that must be resolved before the next release label Oct 5, 2020
@hudson-ayers
Copy link
Contributor

@ppannuto gentle reminder about this

ppannuto added a commit that referenced this issue Nov 11, 2020
Changes since v0.5:

 - #2095: Fix syntax errors and inconsistencies in documentation
 - #2071: Clarify bit widths in documentation examples
 - #2015: Use UnsafeCell in registers (see issue #2005)
 - #1939: Make the Field::mask and FieldValue::mask fields private
 - #1823: Allow large unsigned values as bitmasks + add bitmask! helper macro
 - #1554: Allow lifetime parameters for `register_structs! { Foo<'a> { ..`
 - #1661: Add `Aliased` register type for MMIO with differing R/W behavior

Thanks to @namyoonw, @brghena, @dabross, @gendx, @hudson-ayers, and @pfmooney
for contributions, fixes, and testing!

Closes #2138.
hudson-ayers pushed a commit that referenced this issue Mar 7, 2022
Changes since v0.5:

 - #2095: Fix syntax errors and inconsistencies in documentation
 - #2071: Clarify bit widths in documentation examples
 - #2015: Use UnsafeCell in registers (see issue #2005)
 - #1939: Make the Field::mask and FieldValue::mask fields private
 - #1823: Allow large unsigned values as bitmasks + add bitmask! helper macro
 - #1554: Allow lifetime parameters for `register_structs! { Foo<'a> { ..`
 - #1661: Add `Aliased` register type for MMIO with differing R/W behavior

Thanks to @namyoonw, @brghena, @dabross, @gendx, @hudson-ayers, and @pfmooney
for contributions, fixes, and testing!

Closes #2138.

BUG=none
TEST=make

(cherry picked from commit 72a1e1e)
Change-Id: Ia2dbf69c950e3581a43f5d6601a5cf94abace750
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
release-blocker Issue or PR that must be resolved before the next release
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants