From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Paul Mundt <lethal@linux-sh.org>
Cc: torvalds@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] net/sunrpc/clnt.c compile fix
Date: Thu, 9 Oct 2003 12:50:31 -0400 [thread overview]
Message-ID: <16261.37335.822076.188805@charged.uio.no> (raw)
In-Reply-To: <20031009164048.GA12029@linux-sh.org>
>>>>> " " == Paul Mundt <lethal@linux-sh.org> writes:
> Is there any reason why tk_pid needs to be under RPC_DEBUG in
> the first place? If these are legitimate warning messages,
> presumably it would be nice to know the offending pid as well.
It's not a true process pid, but more of a tag on each struct
rpc_task. It turns out to be more helpful when you are tracing the
(d|)printk() debugging info, since a process may have several rpc_task
in flight at any point in time.
Cheers,
Trond
next prev parent reply other threads:[~2003-10-09 16:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-09 16:13 Paul Mundt
2003-10-09 16:33 ` Geert Uytterhoeven
2003-10-09 16:37 ` Trond Myklebust
2003-10-09 16:40 ` Paul Mundt
2003-10-09 16:50 ` Trond Myklebust [this message]
2003-10-09 16:54 ` Paul Mundt
2003-10-09 16:57 ` Trond Myklebust
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=16261.37335.822076.188805@charged.uio.no \
--to=trond.myklebust@fys.uio.no \
--cc=lethal@linux-sh.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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
all inboxes | Powered by JetHome®