From: David Miller <davem@davemloft.net>
To: philipp_subx@redfish-solutions.com
Cc: bhutchings@solarflare.com, netdev@vger.kernel.org,
linux-atm-general@lists.sourceforge.net
Subject: Re: [PATCH v2 1/1] solos-pci: Fix regression introduced by newest firmware
Date: Sun, 20 Mar 2011 23:04:08 -0700 (PDT) [thread overview]
Message-ID: <20110320.230408.112594622.davem@davemloft.net> (raw)
In-Reply-To: <4D86E89B.1060905@redfish-solutions.com>
From: Philip Prindeville <philipp_subx@redfish-solutions.com>
Date: Sun, 20 Mar 2011 22:56:43 -0700
> It's not clear that dropping all VCs abruptly when carrier flapped was
> ever the right thing to do.
So you've tested your change with the older firmware present?
next prev parent reply other threads:[~2011-03-21 6:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-21 1:52 [PATCH v2 1/1] solos-pci: Fix regression introduced by newest firmware Philip Prindeville
2011-03-21 3:01 ` Ben Hutchings
2011-03-21 4:57 ` David Miller
2011-03-21 5:56 ` Philip Prindeville
2011-03-21 6:04 ` David Miller [this message]
2011-03-21 7:25 ` Philip Prindeville
2011-04-29 23:09 ` [Linux-ATM-General] " David Woodhouse
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=20110320.230408.112594622.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=bhutchings@solarflare.com \
--cc=linux-atm-general@lists.sourceforge.net \
--cc=netdev@vger.kernel.org \
--cc=philipp_subx@redfish-solutions.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).