Closed adamrk closed 4 years ago
Hey Adam, thanks for contributing!
We're slowly migrating ourselves to a plan for contributing this code to the upstream kernel. Would you be interested in migrating your patch to be against https://github.com/Rust-for-Linux/linux/ ?
Yeah, no problem - by the way, is there a chat or something for the Rust-for-Linux group? I've got some questions that don't really make sense to submit as issues.
For example, I'm not sure how to use the library as it is in https://github.com/Rust-for-Linux/linux/ for making a module that's not built-in.
Feel free to just file issues for the time being -- we're working on setting up a mailing list.
On Sat, Oct 17, 2020 at 10:20 AM Adam Bratschi-Kaye < notifications@github.com> wrote:
Yeah, no problem - by the way, is there a chat or something for the Rust-for-Linux group? I've got some questions that don't really make sense to submit as issues.
For example, I'm not sure how to use the library as it is in https://github.com/Rust-for-Linux/linux/ for making a module that's not built-in.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/fishinabarrel/linux-kernel-module-rust/pull/276#issuecomment-711017429, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAAGBEJHOCGMGOMLTAGKA3SLGR4VANCNFSM4SUMJUBA .
-- All that is necessary for evil to succeed is for good people to do nothing.
Hey, I took a stab at adding
fsync
to the file operations. I'm not really sure what the return value is supposed to be used for, so maybe it should just be()
?