From: David Miller <davem@davemloft.net>
To: jeffrey.t.kirsher@intel.com
Cc: khc@pm.waw.pl, netdev@vger.kernel.org,
jesse.brandeburg@intel.com, bruce.w.allan@intel.com,
peter.p.waskiewicz.jr@intel.com, john.ronciak@intel.com,
e1000-devel@lists.sourceforge.net
Subject: Re: Debounce code vs. dma_sync_single_range_for_cpu() and e100 driver.
Date: Thu, 16 Jul 2009 18:09:26 -0700 (PDT) [thread overview]
Message-ID: <20090716.180926.149617102.davem@davemloft.net> (raw)
In-Reply-To: <9929d2390907161527v6ae2751fy31957b643ee0cd88@mail.gmail.com>
From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
Date: Thu, 16 Jul 2009 15:27:01 -0700
> On Tue, Jul 14, 2009 at 2:05 PM, David Miller<davem@davemloft.net> wrote:
>> From: Krzysztof Halasa <khc@pm.waw.pl>
>> Date: Tue, 14 Jul 2009 23:01:54 +0200
>>
>>> Maybe you apply the workaround for 2.6.31 and I (or someone) will
>>> convert e100 to coherent allocs for packet descriptors, post-31?
>>
>> I think that's a good plan.
>>
>> Will give a few days for Intel folks to chime in before applying
>> your patch for 2.6.31, but otherwise that's my plan.
>
> Acked-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
Applied, and queued for -stable, thanks everyone.
prev parent reply other threads:[~2009-07-17 1:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <m31vokbi6p.fsf@intrepid.localdomain>
[not found] ` <20090713181237.GD31979@n2100.arm.linux.org.uk>
2009-07-14 19:34 ` Debounce code vs. dma_sync_single_range_for_cpu() and e100 driver Krzysztof Halasa
2009-07-14 19:38 ` David Miller
2009-07-14 21:01 ` Krzysztof Halasa
2009-07-14 21:05 ` David Miller
2009-07-16 22:27 ` Jeff Kirsher
2009-07-17 1:09 ` David Miller [this message]
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=20090716.180926.149617102.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=bruce.w.allan@intel.com \
--cc=e1000-devel@lists.sourceforge.net \
--cc=jeffrey.t.kirsher@intel.com \
--cc=jesse.brandeburg@intel.com \
--cc=john.ronciak@intel.com \
--cc=khc@pm.waw.pl \
--cc=netdev@vger.kernel.org \
--cc=peter.p.waskiewicz.jr@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox