From: Jesse Barnes <jesse.barnes@intel.com>
To: Hidetoshi Seto <seto.hidetoshi@jp.fujitsu.com>
Cc: linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org,
Jesse Barnes <jbarnes@virtuousgeek.org>
Subject: Re: [PATCH 1/2] pci, msi: Remove unused/obsolete macros and definitions
Date: Tue, 5 May 2009 11:37:39 -0700 [thread overview]
Message-ID: <20090505113739.08d36a89@hobbes> (raw)
In-Reply-To: <49EBD5EC.4040905@jp.fujitsu.com>
On Mon, 20 Apr 2009 10:54:52 +0900
Hidetoshi Seto <seto.hidetoshi@jp.fujitsu.com> wrote:
> Impact: cleanup, spec compliance
>
> This patch does:
>
> - Remove unused msi/msix_enable/disable macros.
> User should use msi/msix_set_enable() functions instead.
>
> - Remove unused msix_mask/unmask/pending macros.
> These macros are useless because they are not based on any of
> the PCI Local Bus Specifications properly.
> It seems that they were written based on a draft of PCI spec,
> and that the draft was the MSI-X ECN that underwent membership
> review in September 2002.
> (* In the draft, the size of a entry in MSI-X table was 64bit,
> containing 32bit message data and DWORD aligned lower address
> plus a pending bit and a mask bit.(30+1+1bit) The higher
> address was placed in MSI-X capability structure and shared
> by all entries.)
>
> - Remove PCI_MSIX_FLAGS_BITMASK.
> This definition also come from the draft ECN.
>
> Signed-off-by: Hidetoshi Seto <seto.hidetoshi@jp.fujitsu.com>
> Cc: Jesse Barnes <jbarnes@virtuousgeek.org>
Applied to my linux-next branch, thanks.
--
Jesse Barnes, Intel Open Source Technology Center
prev parent reply other threads:[~2009-05-05 18:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-20 1:54 Hidetoshi Seto
2009-04-20 11:06 ` Matthew Wilcox
2009-05-05 18:37 ` Jesse Barnes [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=20090505113739.08d36a89@hobbes \
--to=jesse.barnes@intel.com \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=seto.hidetoshi@jp.fujitsu.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
all inboxes | Powered by JetHome®