From: Sergei Shtylyov <sshtylyov@ru.mvista.com>
To: linux-scsi@vger.kernel.org, James.Bottomley@suse.de,
akpm@linux-foundation.org
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH 0/3] SCSI: use pci_dev->revision
Date: Mon, 26 Dec 2011 19:20:47 +0300 [thread overview]
Message-ID: <201112261920.48250.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, or 3.2 time -- hopefully
it can be merged to 3.3 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. Andrew M., as James seem to ignore this patchset, maybe you could
queue it?
WBR, Sergei
next reply other threads:[~2011-12-26 15:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-26 16:20 Sergei Shtylyov [this message]
2011-12-26 16:40 ` [PATCH 0/3] SCSI: use pci_dev->revision Sergei Shtylyov
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=201112261920.48250.sshtylyov@ru.mvista.com \
--to=sshtylyov@ru.mvista.com \
--cc=James.Bottomley@suse.de \
--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