From: Taku Izumi <izumi.taku@jp.fujitsu.com>
To: Jeff Garzik <jeff@garzik.org>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
Tomohiro Kusumi <kusumi.tomohiro@jp.fujitsu.com>,
auke-jan.h.kok@intel.com, jeffrey.t.kirsher@intel.com
Subject: Re: [PATCH 1/3] e1000: make ioport free
Date: Fri, 27 Jun 2008 21:24:03 +0900 [thread overview]
Message-ID: <4864DBE3.3040801@jp.fujitsu.com> (raw)
In-Reply-To: <486483DF.5060404@garzik.org>
Dear Jeff
Jeff Garzik wrote:
> Taku Izumi wrote:
>> This patch makes e1000 driver ioport-free.
>> This corrects behavior in probe function so as not to request ioport
>> resources as long as they are not really needed. This is based on the
>> ioport-free patch of e1000 driver from Auke Kok and Tomohiro Kusumi.
>>
>>
>> Signed-off-by: Tomohiro Kusumi <kusumi.tomohiro@jp.fujitsu.com>
>> Signed-off-by: Auke Kok <auke-jan.h.kok@intel.com>
>> Signed-off-by: Taku Izumi <izumi.taku@jp.fujitsu.com>
>> ---
>> drivers/net/e1000/e1000.h | 4 +
>> drivers/net/e1000/e1000_main.c | 88 +++++++++++++++++++++++++++++++++++------
>> 2 files changed, 80 insertions(+), 12 deletions(-)
>
> ACK but failed to apply
>
I'll re-create one.
Taku Izumi <izumi.taku@jp.fujitsu.com>
next prev parent reply other threads:[~2008-06-27 12:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-20 2:53 [PATCH 0/3] e1000,e1000e,igb: make ioport free for adapters that need NO ioport resources Taku Izumi
2008-06-20 2:55 ` [PATCH 1/3] e1000: make ioport free Taku Izumi
2008-06-27 6:08 ` Jeff Garzik
2008-06-27 12:24 ` Taku Izumi [this message]
2008-06-27 13:05 ` Taku Izumi
2008-06-27 17:08 ` Jeff Kirsher
2008-06-20 2:57 ` [PATCH 2/3] e1000e: " Taku Izumi
2008-06-23 8:32 ` Taku Izumi
2008-06-27 6:08 ` Jeff Garzik
2008-06-20 3:10 ` [PATCH 3/3] igb: " Taku Izumi
2008-06-23 8:32 ` Taku Izumi
2008-06-21 18:19 ` [PATCH 0/3] e1000,e1000e,igb: make ioport free for adapters that need NO ioport resources Kok, Auke
2008-06-23 8:28 ` Taku Izumi
2008-06-23 23:40 ` Jeff Kirsher
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=4864DBE3.3040801@jp.fujitsu.com \
--to=izumi.taku@jp.fujitsu.com \
--cc=auke-jan.h.kok@intel.com \
--cc=jeff@garzik.org \
--cc=jeffrey.t.kirsher@intel.com \
--cc=kusumi.tomohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--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).