From: Rusty Russell <rusty@rustcorp.com.au>
To: Jiri Slaby <jslaby@suse.cz>, jirislaby@gmail.com
Cc: linux-kernel@vger.kernel.org, Jiri Slaby <jslaby@suse.cz>
Subject: Re: [PATCH 2/2] module: use pr_cont
Date: Mon, 27 Jan 2014 22:07:54 +1030 [thread overview]
Message-ID: <871tzt1wq5.fsf@rustcorp.com.au> (raw)
In-Reply-To: <1390814884-15519-2-git-send-email-jslaby@suse.cz>
Jiri Slaby <jslaby@suse.cz> writes:
> When dumping loaded modules, we print them one by one in separate
> printks. Let's use pr_cont as they are continuation prints.
Applied.
Thanks,
Rusty.
prev parent reply other threads:[~2014-01-27 11:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-27 9:28 [PATCH 1/2] x86: dumpstack, use pr_cont Jiri Slaby
2014-01-27 9:28 ` [PATCH 2/2] module: " Jiri Slaby
2014-01-27 11:37 ` Rusty Russell [this message]
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=871tzt1wq5.fsf@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=jirislaby@gmail.com \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.org \
/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