From: Marek Vasut <marex@denx.de>
To: "Myklebust, Trond" <Trond.Myklebust@netapp.com>
Cc: Fabio Estevam <fabio.estevam@freescale.com>,
"davem@davemloft.net" <davem@davemloft.net>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH] net: sunrpc: xdr: Change message to pr_debug level
Date: Thu, 4 Oct 2012 16:57:58 +0200 [thread overview]
Message-ID: <201210041657.59046.marex@denx.de> (raw)
In-Reply-To: <4FA345DA4F4AE44899BD2B03EEEC2FA9090049AD@SACEXCMBX04-PRD.hq.netapp.com>
Dear Myklebust, Trond,
> > -----Original Message-----
> > From: Marek Vasut [mailto:marex@denx.de]
> > Sent: Thursday, October 04, 2012 7:25 AM
> > To: Fabio Estevam
> > Cc: davem@davemloft.net; Myklebust, Trond; netdev@vger.kernel.org;
> > linux-nfs@vger.kernel.org
> > Subject: Re: [PATCH] net: sunrpc: xdr: Change message to pr_debug level
> >
> > Dear Fabio Estevam,
> >
> > > commit 49f6189 (SUNRPC: Optimise away unnecessary data moves in
> > > xdr_align_pages) has added a pr_info that floods dmesg when booting
> > > via NFS.
> > >
> > > There is also a note in the commit log: "Warning! Contains debugging
> > > printks!"
>
> ...which meant that it contained debugging code, and was obviously not
> appropriate for merging upstream. The final version has already dropped
> the debugging printks.
Uh oh, the version with debug prints made it into -next .
Best regards,
Marek Vasut
prev parent reply other threads:[~2012-10-04 14:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-04 14:21 [PATCH] net: sunrpc: xdr: Change message to pr_debug level Fabio Estevam
[not found] ` <1349360495-29325-1-git-send-email-fabio.estevam-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
2012-10-04 14:25 ` Marek Vasut
2012-10-04 14:51 ` Myklebust, Trond
2012-10-04 14:57 ` Marek Vasut [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=201210041657.59046.marex@denx.de \
--to=marex@denx.de \
--cc=Trond.Myklebust@netapp.com \
--cc=davem@davemloft.net \
--cc=fabio.estevam@freescale.com \
--cc=linux-nfs@vger.kernel.org \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).