From: dusan3sic@gmail.com
To: 9fans <9fans@9fans.net>
Subject: Re: [9fans] print() in kernel space doesn't work like I would think
Date: Fri, 1 Sep 2023 06:59:28 -0400 [thread overview]
Message-ID: <16935659680.57e0.289388@composer.9fans.topicbox.com> (raw)
In-Reply-To: <34E2D05F20FF69DF77D364CE7EBEB653@eigenstate.org>
[-- Attachment #1: Type: text/plain, Size: 311 bytes --]
I tried actually running some realtime processes and the print msg appeared. Thanks
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/Te1d00dae663114b2-M0b15b6c18936d12d96aa47dc
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
[-- Attachment #2: Type: text/html, Size: 805 bytes --]
next prev parent reply other threads:[~2023-09-01 10:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-31 15:43 dusan3sic
2023-08-31 15:48 ` Steve Simon
2023-08-31 16:27 ` ori
2023-08-31 16:31 ` ori
2023-08-31 16:46 ` dusan3sic
2023-08-31 16:58 ` dusan3sic
2023-08-31 17:25 ` dusan3sic
2023-08-31 17:34 ` ori
2023-09-01 10:59 ` dusan3sic [this message]
2023-08-31 19:42 ` ori
2023-08-31 16:53 ` dusan3sic
2023-08-31 17:20 ` ori
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=16935659680.57e0.289388@composer.9fans.topicbox.com \
--to=dusan3sic@gmail.com \
--cc=9fans@9fans.net \
/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).