diff options
| -rw-r--r-- | CITATION.cff | 2 | ||||
| -rw-r--r-- | source/wg01/paper.tex | 6 | ||||
| -rw-r--r-- | source/wg02/paper.tex | 2 |
3 files changed, 5 insertions, 5 deletions
diff --git a/CITATION.cff b/CITATION.cff index 26c35c6..56b4cf4 100644 --- a/CITATION.cff +++ b/CITATION.cff @@ -10,7 +10,7 @@ identifiers: - type: url value: 'https://nekernel.org' description: NeKernel.org -repository-code: 'https://github.com/nekernel-org/papers' +repository-code: 'https://github.com/ne-foss-org/papers' url: 'https://nekernel.org' abstract: >- Working Group Papers of NeKernel.org, authored by Amlal El Mahrouss. diff --git a/source/wg01/paper.tex b/source/wg01/paper.tex index 931e80b..61cf29d 100644 --- a/source/wg01/paper.tex +++ b/source/wg01/paper.tex @@ -85,7 +85,7 @@ struct MemoryTree final { static constexpr bool is_file = false; /// ... }; -\end{lstlisting} Source: \href{https://github.com/nekernel-org/nekernel/blob/develop/src/kernel/KernelKit/CoreProcessScheduler.h#L78-L105}{Link}. \\ Which is why the `constexpr' keyword is very powerful here for the Compile-Time Evaluation Domain, we avoid the many pitfalls of the Run-Time Evaluation Domain. +\end{lstlisting} Source: \href{https://github.com/ne-foss-org/nekernel/blob/develop/src/kernel/KernelKit/CoreProcessScheduler.h#L78-L105}{Link}. \\ Which is why the `constexpr' keyword is very powerful here for the Compile-Time Evaluation Domain, we avoid the many pitfalls of the Run-Time Evaluation Domain. \subsection{III: Memory Layout and the example of C++.} { @@ -128,7 +128,7 @@ template <class Driver> concept IsValidDriver = requires(Driver drv) { { drv.IsActive() && drv.Type() > kInvalidType }; }; -\end{lstlisting} Source: \href{https://github.com/nekernel-org/nekernel/blob/develop/src/libDDK/DriverKit/c%2B%2B/driver_base.h}{Link}.\\ Now, the problem with freestanding development is that such feature may be abused, and it is mitigated by following the TTPI. +\end{lstlisting} Source: \href{https://github.com/ne-foss-org/nekernel/blob/develop/src/libDDK/DriverKit/c%2B%2B/driver_base.h}{Link}.\\ Now, the problem with freestanding development is that such feature may be abused, and it is mitigated by following the TTPI. \subsection{IV: The Three Prongs on Inheritance.} @@ -173,7 +173,7 @@ if constexpr (IsVettable<UnVettable>) { } else { instVet->Abort(); } -\end{lstlisting} Source: \href{https://github.com/nekernel-org/nekernel/blob/develop/src/kernel/NeKit/Vettable.h}{Link}. +\end{lstlisting} Source: \href{https://github.com/ne-foss-org/nekernel/blob/develop/src/kernel/NeKit/Vettable.h}{Link}. \section{VI: Conclusion} { Safe and correct development in a freestanding domain is indeed possible granted the above concepts are applied and respected.} diff --git a/source/wg02/paper.tex b/source/wg02/paper.tex index 4f49ab5..c6dd487 100644 --- a/source/wg02/paper.tex +++ b/source/wg02/paper.tex @@ -155,7 +155,7 @@ struct ProcessImage final { \section{References} \begin{enumerate} - \item CoreProcessScheduler.h (2025), \href{https://github.com/nekernel-org/nekernel/blob/develop/src/kernel/KernelKit/CoreProcessScheduler.h}{github.com} + \item CoreProcessScheduler.h (2025), \href{https://github.com/ne-foss-org/nekernel/blob/develop/src/kernel/KernelKit/CoreProcessScheduler.h}{github.com} \item NeKernel.org (2025), \href{https://nekernel.org/nekernel}{nekernel.org} \item Scheduling: Introduction (2012), \href{https://pages.cs.wisc.edu/~remzi/OSTEP/cpu-sched.pdf}{pages.cs.wisc.edu} |