From: "Onur Özkan" <work@onurozkan.dev>
To: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
Cc: rust-for-linux@vger.kernel.org, ojeda@kernel.org,
alex.gaynor@gmail.com, boqun.feng@gmail.com, gary@garyguo.net,
bjorn3_gh@protonmail.com, lossin@kernel.org,
a.hindborg@kernel.org, aliceryhl@google.com, tmgross@umich.edu,
dakr@kernel.org, me@kloenk.dev, felipe_life@live.com,
abdiel.janulgue@gmail.com, dirk.behme@de.bosch.com,
daniel@sedlak.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] rust: update `error.rs` documentation
Date: Wed, 30 Jul 2025 13:00:30 +0300 [thread overview]
Message-ID: <20250730130030.12d03ca6@nimda.home> (raw)
In-Reply-To: <CANiq72=L_ov+Dc5S=adPdson9gq6wGp4xp=iCZLBnz+YC1_vgw@mail.gmail.com>
On Tue, 29 Jul 2025 21:35:06 +0200
Miguel Ojeda <miguel.ojeda.sandonis@gmail.com> wrote:
> On Tue, Jul 29, 2025 at 4:36 PM Onur Özkan <work@onurozkan.dev> wrote:
> >
> > Replaces the outdated (e.g., `ENOIOCTLCMD` is in the
> > `srctree/include/linux/errno.h` file) and overly specific
> > description referring to a single C header with a more generic
> > one.
>
> Yeah, we should have the other headers there, but I would avoid
> removing the links entirely (the links are meant to be there as a
> reference and get converted to actual links on render).
>
> Thanks!
>
> Cheers,
> Miguel
I thought with that approach the documentation can become outdated
again at some point, but I can still do it and send over v2 if you
would prefer.
Regards,
Onur
next prev parent reply other threads:[~2025-07-30 10:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-29 14:36 [PATCH v1] rust: update `error.rs` documentation Onur Özkan
2025-07-29 19:35 ` Miguel Ojeda
2025-07-30 10:00 ` Onur Özkan [this message]
2025-07-30 11:01 ` Miguel Ojeda
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250730130030.12d03ca6@nimda.home \
--to=work@onurozkan.dev \
--cc=a.hindborg@kernel.org \
--cc=abdiel.janulgue@gmail.com \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=dakr@kernel.org \
--cc=daniel@sedlak.dev \
--cc=dirk.behme@de.bosch.com \
--cc=felipe_life@live.com \
--cc=gary@garyguo.net \
--cc=linux-kernel@vger.kernel.org \
--cc=lossin@kernel.org \
--cc=me@kloenk.dev \
--cc=miguel.ojeda.sandonis@gmail.com \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=tmgross@umich.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox