From: Matthew Wilcox <matthew@wil.cx>
To: David Miller <davem@davemloft.net>
Cc: jeffrey.t.kirsher@intel.com, netdev@vger.kernel.org,
gospo@redhat.com, alexander.h.duyck@intel.com,
linux-pci@vger.kernel.org, willy@linux.intel.com,
jbarnes@virtuousgeek.org
Subject: Re: [net-next PATCH 1/2] PCI: Add PCI quirk to disable L0s ASPM state for 82575 and 82598
Date: Thu, 5 Mar 2009 18:02:07 -0700 [thread overview]
Message-ID: <20090306010207.GA829@parisc-linux.org> (raw)
In-Reply-To: <20090305.163108.70528099.davem@davemloft.net>
On Thu, Mar 05, 2009 at 04:31:08PM -0800, David Miller wrote:
> From: Matthew Wilcox <matthew@wil.cx>
> Date: Tue, 3 Mar 2009 21:05:26 -0700
>
> > I'm not going to ack this patch at this point, let's just give it a day.
>
> More than a day has passed, how long are we going to let this
> patch sit and rot?
>
> Do we have to wait until Jesse gets back? That doesn't sound
> reasonable to me.
A lot of the discussion on this happened face-to-face; Jeff, Linus and I
were all at the same conference this week. I have put it in a pci fixes
tree, which I now have to pull apart again because one of the earlier
patches needs to be dropped. I'm getting on a plane tonight and flying
home, so I'll be pushing this fix to Linus tomorrow.
Sorry for not keeping you in the loop on this one.
--
Matthew Wilcox Intel Open Source Technology Centre
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours. We can't possibly take such
a retrograde step."
next prev parent reply other threads:[~2009-03-06 1:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-04 2:03 [net-next PATCH 1/2] PCI: Add PCI quirk to disable L0s ASPM state for 82575 and 82598 Jeff Kirsher
2009-03-04 2:03 ` [net-next PATCH 2/2] igb: remove ASPM L0s workaround Jeff Kirsher
2009-03-04 4:05 ` [net-next PATCH 1/2] PCI: Add PCI quirk to disable L0s ASPM state for 82575 and 82598 Matthew Wilcox
2009-03-06 0:31 ` David Miller
2009-03-06 1:02 ` Matthew Wilcox [this message]
2009-03-06 1:44 ` David Miller
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=20090306010207.GA829@parisc-linux.org \
--to=matthew@wil.cx \
--cc=alexander.h.duyck@intel.com \
--cc=davem@davemloft.net \
--cc=gospo@redhat.com \
--cc=jbarnes@virtuousgeek.org \
--cc=jeffrey.t.kirsher@intel.com \
--cc=linux-pci@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=willy@linux.intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.