rust: use <> link style in comments too

This is intended to follow our "use Markdown for comments too"
/ "comments and docs should be easily interchangeable" guideline.

Signed-off-by: Miguel Ojeda <ojeda@kernel.org>

Author: ojeda

rust/bindings/lib.rs

@@ -10,7 +10,7 @@
 
 #![no_std]
 #![feature(core_ffi_c)]
-// See https://github.com/rust-lang/rust-bindgen/issues/1651.
+// See <https://github.com/rust-lang/rust-bindgen/issues/1651>.
 #![cfg_attr(test, allow(deref_nullptr))]
 #![cfg_attr(test, allow(unaligned_references))]
 #![cfg_attr(test, allow(unsafe_op_in_unsafe_fn))]

rust/kernel/file.rs

@@ -335,7 +335,7 @@ impl<A: OpenAdapter<T::OpenData>, T: Operations> OperationsVtable<A, T> {
             // function is running.
             let f = unsafe { T::Data::borrow((*file).private_data) };
             // No `FMODE_UNSIGNED_OFFSET` support, so `offset` must be in [0, 2^63).
-            // See discussion in https://github.com/fishinabarrel/linux-kernel-module-rust/pull/113
+            // See <https://github.com/fishinabarrel/linux-kernel-module-rust/pull/113>.
             let read = T::read(
                 f,
                 unsafe { File::from_ptr(file) },
@@ -388,7 +388,7 @@ impl<A: OpenAdapter<T::OpenData>, T: Operations> OperationsVtable<A, T> {
             // function is running.
             let f = unsafe { T::Data::borrow((*file).private_data) };
             // No `FMODE_UNSIGNED_OFFSET` support, so `offset` must be in [0, 2^63).
-            // See discussion in https://github.com/fishinabarrel/linux-kernel-module-rust/pull/113
+            // See <https://github.com/fishinabarrel/linux-kernel-module-rust/pull/113>.
             let written = T::write(
                 f,
                 unsafe { File::from_ptr(file) },

rust/kernel/kasync/net.rs

@@ -199,7 +199,7 @@ impl<'a, Out, F: FnMut() -> Result<Out> + Send + 'a> SocketFuture<'a, Out, F> {
         // There is a potential soundness issue here because we're generating a shared reference to
         // `Self` while `Self::poll` has a mutable (unique) reference. However, for `!Unpin` types
         // (like `Self`), `&mut T` is treated as `*mut T` per
-        // https://github.com/rust-lang/rust/issues/63818 -- so we avoid the unsoundness. Once a
+        // <https://github.com/rust-lang/rust/issues/63818> -- so we avoid the unsoundness. Once a
         // more definitive solution is available, we can change this to use it.
         let s = unsafe { &*crate::container_of!(wq_entry, Self, wq_entry) };
         if mask & s.mask == 0 {

rust/kernel/lib.rs

@@ -262,7 +262,6 @@ fn panic(info: &core::panic::PanicInfo<'_>) -> ! {
     // SAFETY: FFI call.
     unsafe { bindings::BUG() };
     // Bindgen currently does not recognize `__noreturn` so `BUG` returns `()`
-    // instead of `!`.
-    // https://github.com/rust-lang/rust-bindgen/issues/2094
+    // instead of `!`. See <https://github.com/rust-lang/rust-bindgen/issues/2094>.
     loop {}
 }

rust/kernel/sync/guard.rs

@@ -21,7 +21,7 @@ pub struct Guard<'a, L: Lock<I> + ?Sized, I: LockInfo = WriteLock> {
 
 // SAFETY: `Guard` is sync when the data protected by the lock is also sync. This is more
 // conservative than the default compiler implementation; more details can be found on
-// https://github.com/rust-lang/rust/issues/41622 -- it refers to `MutexGuard` from the standard
+// <https://github.com/rust-lang/rust/issues/41622> -- it refers to `MutexGuard` from the standard
 // library.
 unsafe impl<L, I> Sync for Guard<'_, L, I>
 where