netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: chris.mason@oracle.com
Cc: nhorman@tuxdriver.com, netdev@vger.kernel.org,
	rds-devel@oss.oracle.com, venkat.x.venkatsubra@oracle.com
Subject: Re: [rds-devel] [PATCH] rds: prevent BUG_ON triggering on congestion map updates
Date: Tue, 08 Mar 2011 10:52:23 -0800 (PST)	[thread overview]
Message-ID: <20110308.105223.71117584.davem@davemloft.net> (raw)
In-Reply-To: <1299530363-sup-8922@think>

From: Chris Mason <chris.mason@oracle.com>
Date: Mon, 07 Mar 2011 15:41:04 -0500

> Excerpts from David Miller's message of 2011-03-07 15:27:53 -0500:
>> From: Neil Horman <nhorman@tuxdriver.com>
>> Date: Wed,  2 Mar 2011 11:28:22 -0500
>> 
>> > Recently had this bug halt reported to me:
>> 
>> Well, does anyone on the RDS team care about this bug fix at all?
>> 
>> Stuff like this should not sit for nearly a week without any reply
>> whatsoever.
>> 
> 
> The patch looks good to me, but I'm surprised we haven't seen it here.
> Venkat please take a look (link to the patch below)  Has it only been seen on ppc?
> 
> http://permalink.gmane.org/gmane.linux.network/187933

Can I get an ACK or something, _please_?

  parent reply	other threads:[~2011-03-08 18:51 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-02 16:28 [PATCH] rds: prevent BUG_ON triggering on congestion map updates Neil Horman
2011-03-07 20:27 ` David Miller
2011-03-07 20:41   ` [rds-devel] " Chris Mason
2011-03-07 20:56     ` Neil Horman
2011-03-08 18:52     ` David Miller [this message]
2011-03-08 18:58       ` Chris Mason
2011-03-08 19:22         ` David Miller
2011-03-08 19:36           ` Neil Horman
  -- strict thread matches above, loose matches on Subject: below --
2011-03-08 23:36 Venkat Venkatsubra

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=20110308.105223.71117584.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=chris.mason@oracle.com \
    --cc=netdev@vger.kernel.org \
    --cc=nhorman@tuxdriver.com \
    --cc=rds-devel@oss.oracle.com \
    --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).