From: David Miller <davem@davemloft.net>
To: davej@redhat.com
Cc: venkat.x.venkatsubra@oracle.com, netdev@vger.kernel.org
Subject: Re: Remove printk from rds_sendmsg
Date: Tue, 20 Mar 2012 16:12:59 -0400 (EDT) [thread overview]
Message-ID: <20120320.161259.1804504946572194386.davem@davemloft.net> (raw)
In-Reply-To: <20120319230107.GA23987@redhat.com>
From: Dave Jones <davej@redhat.com>
Date: Mon, 19 Mar 2012 19:01:07 -0400
> no socket layer outputs a message for this error and neither should rds.
>
> Signed-off-by: Dave Jones <davej@redhat.com>
Applied and queued up for -stable, thanks.
next prev parent reply other threads:[~2012-03-20 20:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-19 22:40 Improve rds_sendmsg printk Dave Jones
2012-03-19 22:43 ` David Miller
2012-03-19 23:01 ` Remove printk from rds_sendmsg Dave Jones
2012-03-20 20:12 ` David Miller [this message]
2012-03-20 14:50 ` Improve rds_sendmsg printk Venkat Venkatsubra
2012-03-19 23:08 ` Joe Perches
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=20120320.161259.1804504946572194386.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=davej@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=venkat.x.venkatsubra@oracle.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;
as well as URLs for NNTP newsgroup(s).