From: Jeff Garzik <jgarzik@pobox.com>
To: Stephen Hemminger <shemminger@linux-foundation.org>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH 1/3] sky2: revert to access PCI config via device space
Date: Sat, 01 Dec 2007 16:34:14 -0500 [thread overview]
Message-ID: <4751D356.7060606@pobox.com> (raw)
In-Reply-To: <20071127105727.1bcfa56f@freepuppy.rosehill>
Stephen Hemminger wrote:
> Using the hardware window into PCI config space is more reliable
> and smaller/faster than using the pci_config routines. It avoids issues
> with MMCONFIG etc.
>
> Reverts: 167f53d05fccb47b6eeadac7f6705b3f2f042d03
>
> Please apply for 2.6.24
>
> Signed-off-by: Stephen Hemminger <shemminger@linux-foundation.org>
applied 1-3
prev parent reply other threads:[~2007-12-01 21:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-27 18:57 [PATCH 1/3] sky2: revert to access PCI config via device space Stephen Hemminger
[not found] ` <20071127110036.0268c0a9@freepuppy.rosehill>
2007-11-27 19:02 ` [PATCH 3/3] sky2: turn of dynamic Tx watermark workaround (FE+ only) Stephen Hemminger
2007-11-27 19:02 ` [PATCH 2/3] sky2: don't use AER routines Stephen Hemminger
2007-12-01 21:34 ` Jeff Garzik [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=4751D356.7060606@pobox.com \
--to=jgarzik@pobox.com \
--cc=netdev@vger.kernel.org \
--cc=shemminger@linux-foundation.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).