public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <randy.dunlap-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
To: Trond Myklebust
	<Trond.Myklebust-HgOvQuBEEgTQT0dZR+AlfA@public.gmane.org>
Cc: Alexander Beregalov
	<a.beregalov-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
	linux-next-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-nfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH next-20090316] sunrpc: fix build breakage
Date: Wed, 18 Mar 2009 08:56:28 -0700	[thread overview]
Message-ID: <20090318085628.36eea73c.randy.dunlap@oracle.com> (raw)
In-Reply-To: <1237208680.7229.14.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>

On Mon, 16 Mar 2009 09:04:40 -0400 Trond Myklebust wrote:

> On Mon, 2009-03-16 at 15:51 +0300, Alexander Beregalov wrote:
> > net/sunrpc/clnt.c: In function 'call_bind_status':
> > net/sunrpc/clnt.c:994: error: 'struct rpc_task' has no member named
> > 'tk_pid'
> > net/sunrpc/clnt.c: In function 'call_connect_status':
> > net/sunrpc/clnt.c:1051: error: 'struct rpc_task' has no member named
> > 'tk_pid'
> > 
> > rpc_task has tk_pid if RPC_DEBUG is defined.
> > 
> > Signed-off-by: Alexander Beregalov <a.beregalov-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
> > ---
> > 
> >  net/sunrpc/clnt.c |    4 ++--
> >  1 files changed, 2 insertions(+), 2 deletions(-)
> > 
> > diff --git a/net/sunrpc/clnt.c b/net/sunrpc/clnt.c
> > index efd0c7b..68cb91a 100644
> > --- a/net/sunrpc/clnt.c
> > +++ b/net/sunrpc/clnt.c
> > @@ -990,7 +990,7 @@ call_bind_status(struct rpc_task *task)
> >  		return;
> >  	default:
> >  		if (net_ratelimit())
> > -			printk("RPC: %5u unrecognized rpcbind error (%d)\n",
> > +			dprintk("RPC: %5u unrecognized rpcbind error (%d)\n",
> >  					task->tk_pid, -task->tk_status);
> >  	}
> >  
> > @@ -1047,7 +1047,7 @@ call_connect_status(struct rpc_task *task)
> >  		break;
> >  	default:
> >  		if (net_ratelimit())
> > -			printk("RPC: %5u unrecognized connect error (%d)\n",
> > +			dprintk("RPC: %5u unrecognized connect error (%d)\n",
> >  					task->tk_pid, status);
> >  		rpc_exit(task, -EIO);
> >  	}
> 
> No, that's not right. The intention is to always report errors that are
> fatal and are due to unforeseen circumstances. Your patch means that
> those reports are suppressed entirely when RPC_DEBUG is undefined.


nevertheless, the build breakage is still around in linux-next 20090318...

---
~Randy
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      parent reply	other threads:[~2009-03-18 15:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-16 12:51 [PATCH next-20090316] sunrpc: fix build breakage Alexander Beregalov
2009-03-16 13:04 ` Trond Myklebust
     [not found]   ` <1237208680.7229.14.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2009-03-18 15:56     ` Randy Dunlap [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=20090318085628.36eea73c.randy.dunlap@oracle.com \
    --to=randy.dunlap-qhclzuegtsvqt0dzr+alfa@public.gmane.org \
    --cc=Trond.Myklebust-HgOvQuBEEgTQT0dZR+AlfA@public.gmane.org \
    --cc=a.beregalov-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=linux-next-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-nfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.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