From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org, gospo@redhat.com, bruce.w.allan@intel.com
Subject: Re: [net-2.6 PATCH 1/5] e1000e: call pci_save_state() after pci_restore_state()
Date: Thu, 7 Jan 2010 23:59:32 -0800 [thread overview]
Message-ID: <9929d2391001072359u499b3269v9b0c1cd6ca864798@mail.gmail.com> (raw)
In-Reply-To: <20100107.235240.173918660.davem@davemloft.net>
On Thu, Jan 7, 2010 at 23:52, David Miller <davem@davemloft.net> wrote:
>
> Aren't the fragment overrun patches for e1000 and e1000e 1,000 times
> more important that thumb twiddling fixes like these? :-(
> --
I would agree, and Jesse's updated patches which were made 1 day ago
are currently under test and review, where as these patches were
produced over Christmas break and testing was completed before Jesse
completed his rework of the fragment overrun patches (and are based on
a driver which has these patches applied).
--
Cheers,
Jeff
next prev parent reply other threads:[~2010-01-08 7:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-08 2:30 [net-2.6 PATCH 1/5] e1000e: call pci_save_state() after pci_restore_state() Jeff Kirsher
2010-01-08 2:31 ` [net-2.6 PATCH 2/5] e1000e: don't accumulate PHY statistics on PHY read failure Jeff Kirsher
2010-01-08 8:39 ` David Miller
2010-01-08 2:31 ` [net-2.6 PATCH 3/5] e1000e: perform 10/100 adaptive IFS only on parts that support it Jeff Kirsher
2010-01-08 8:39 ` David Miller
2010-01-08 2:31 ` [net-2.6 PATCH 4/5] e1000e: e1000e_enable_tx_pkt_filtering() returns wrong value Jeff Kirsher
2010-01-08 8:39 ` David Miller
2010-01-08 2:32 ` [net-2.6 PATCH 5/5] e1000e: fix and commonize code for setting the receive address registers Jeff Kirsher
2010-01-08 8:39 ` David Miller
2010-01-08 7:52 ` [net-2.6 PATCH 1/5] e1000e: call pci_save_state() after pci_restore_state() David Miller
2010-01-08 7:59 ` Jeff Kirsher [this message]
2010-01-08 8:39 ` 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=9929d2391001072359u499b3269v9b0c1cd6ca864798@mail.gmail.com \
--to=jeffrey.t.kirsher@intel.com \
--cc=bruce.w.allan@intel.com \
--cc=davem@davemloft.net \
--cc=gospo@redhat.com \
--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).