Skip to content

Resolve doxygen warning in filesystems docs #5395

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

Merged

Conversation

kegilbert
Copy link
Contributor

Came up while writing docs for the filesystem APIs that we had class references for all blockdevice classes but ProfilingBlockDevice. @AnotherButler mentioned we had removed filesystems once from the doxygen exclusion list, so looks like we had all but that file generated before it was added back to the exclusion list.

Fixed the one warning we had in doxygen, @sg- was there a reason features/filesystem should be on the exclusion list other than the previous warnings?

@sg-
Copy link
Contributor

sg- commented Oct 28, 2017

Fixed the one warning we had in doxygen, @sg- was there a reason features/filesystem should be on the exclusion list other than the previous warnings?

Nope.

@adbridge
Copy link
Contributor

/morph build

@mbed-ci
Copy link

mbed-ci commented Oct 30, 2017

Build : SUCCESS

Build number : 368
Build artifacts/logs : http://mbed-os.s3-website-eu-west-1.amazonaws.com/?prefix=builds/5395/

Triggering tests

/morph test
/morph uvisor-test

@mbed-ci
Copy link

mbed-ci commented Oct 30, 2017

@mbed-ci
Copy link

mbed-ci commented Oct 31, 2017

Build : SUCCESS

Build number : 392
Build artifacts/logs : http://mbed-os.s3-website-eu-west-1.amazonaws.com/?prefix=builds/5395/

Triggering tests

/morph test
/morph uvisor-test

@mbed-ci
Copy link

mbed-ci commented Oct 31, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants