From: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
To: se iro <seiro22@mailfence.com>
Cc: rust-for-linux@vger.kernel.org
Subject: Re: leaky info and kernel modules
Date: Thu, 8 Apr 2021 00:12:51 +0200 [thread overview]
Message-ID: <CANiq72n3+CSSGVUzjuDzHdH2p_6ucug+FKSHButbwPgCjswAeA@mail.gmail.com> (raw)
In-Reply-To: <CANiq72nWvusyKf_N2N8i+de5HA-UZYfFPUrp9taRFbXya5h18w@mail.gmail.com>
On Wed, Apr 7, 2021 at 11:50 PM Miguel Ojeda
<miguel.ojeda.sandonis@gmail.com> wrote:
>
> I will create a quick issue about this.
Done:
https://github.com/Rust-for-Linux/linux/issues/169
Cheers,
Miguel
next prev parent reply other threads:[~2021-04-07 22:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-07 14:22 leaky info and kernel modules se iro
2021-04-07 16:50 ` Geoffrey Thomas
2021-04-07 21:50 ` Miguel Ojeda
2021-04-07 22:12 ` Miguel Ojeda [this message]
2021-04-08 2:38 ` se iro
2021-04-08 6:35 ` 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=CANiq72n3+CSSGVUzjuDzHdH2p_6ucug+FKSHButbwPgCjswAeA@mail.gmail.com \
--to=miguel.ojeda.sandonis@gmail.com \
--cc=rust-for-linux@vger.kernel.org \
--cc=seiro22@mailfence.com \
/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;
as well as URLs for NNTP newsgroup(s).