From: Sergei Shtylyov <sshtylyov@ru.mvista.com>
To: linux-scsi@vger.kernel.org, JBottomley@parallels.com,
akpm@linux-foundation.org
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH 0/3 v2] SCSI: use pci_dev->revision
Date: Wed, 14 Mar 2012 22:01:39 +0300 [thread overview]
Message-ID: <201203142201.39728.sshtylyov@ru.mvista.com> (raw)
Hello.
This patchset converts the remaining cases of reading the PCI revision register
directly to using the value already cached by PCI subsystem in the 'revision'
field of 'struct pci_dev'.
The patchset wasn't merged in either 2.6.39, 3.0, 3.1, 3.2, or 3.3 time --
hopefully it can be merged to 3.4 at least...
James B., you seem to consistently ignore this patchset without telling me what
is wrong with it; in all my attempts at submitting it I got no feedback what
so ever (except ACK on patch 3 from Vikas Chaudhary).
Andrew M., as James seem to ignore this patchset, maybe you could queue it?
All the analogous patches to other sybsystems (except these three to the SCSI
subsystem and to the Fusion MPT driver) have been merged long ago, without much
hassle...
MBR, Sergei
PS: I'm beginning to lose hope/temper... :-/
reply other threads:[~2012-03-14 18:02 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=201203142201.39728.sshtylyov@ru.mvista.com \
--to=sshtylyov@ru.mvista.com \
--cc=JBottomley@parallels.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@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