summaryrefslogtreecommitdiffhomepage
path: root/source
diff options
context:
space:
mode:
authorAmlal El Mahrouss <amlal@nekernel.org>2026-03-02 15:13:45 +0100
committerAmlal El Mahrouss <amlal@nekernel.org>2026-03-02 15:13:45 +0100
commit339e71a94fc358ed46228eae2b7870bdcbdc1c66 (patch)
tree38b368167a840421c40249faa396db324f20a7e7 /source
parent0ed8c33e860b3ccc80f5b6e6fdb0dd4c0f23ad47 (diff)
chore: upstream fixes.
Signed-off-by: Amlal El Mahrouss <amlal@nekernel.org>
Diffstat (limited to 'source')
-rw-r--r--source/wg01/paper.tex6
-rw-r--r--source/wg02/paper.tex2
2 files changed, 4 insertions, 4 deletions
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}