From: Wedson Almeida Filho <wedsonaf@google.com>
To: Carlos <carloscarral13@gmail.com>
Cc: rust-for-linux@vger.kernel.org,
Greg KH <gregkh@linuxfoundation.org>,
Sven Van Asbroeck <thesven73@gmail.com>
Subject: Re: Loading an out-of-tree module
Date: Thu, 29 Apr 2021 17:05:22 +0100 [thread overview]
Message-ID: <YIrZQk6eTNUiQa/I@google.com> (raw)
In-Reply-To: <YIrXFt2KVovbM+Fs@localhost.localdomain>
On Thu, Apr 29, 2021 at 10:56:06AM -0500, Carlos wrote:
> I get why the OOT flag is there so I won't try to remove it. What
> concerns me, however, is that my printk messages don't work as expected
> (i.e. They are one off). Is this behaviour caused by the same flag?
Adding a new line (\n) to the end of your messages should fix this.
Cheers,
-Wedson
next prev parent reply other threads:[~2021-04-29 16:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-29 14:32 Loading an out-of-tree module Carlos
2021-04-29 14:38 ` Sven Van Asbroeck
2021-04-29 14:52 ` Sven Van Asbroeck
2021-04-29 15:16 ` Greg KH
2021-04-29 15:56 ` Carlos
2021-04-29 16:05 ` Wedson Almeida Filho [this message]
2021-04-29 16:06 ` 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=YIrZQk6eTNUiQa/I@google.com \
--to=wedsonaf@google.com \
--cc=carloscarral13@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=thesven73@gmail.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