linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paolo <paolopiace@gmail.com>
To: linux-pci@vger.kernel.org
Subject: Re: accessing pci_dev
Date: Mon, 6 Aug 2012 23:16:32 +0000 (UTC)	[thread overview]
Message-ID: <loom.20120807T010348-354@post.gmane.org> (raw)
In-Reply-To: 20120806224658.GA8579@kroah.com

Greg KH <gregkh <at> linuxfoundation.org> writes:
> 
> Yes, but why would you?
> 
> What problem are you trying to solve?
>

Thanks for responding!

Basically, I want to check the config registers before and after the driver
registration in order to make sure that the driver is not contaminating them.

And, yes, it's the very first time I'm dealing with kernel & drivers.


  reply	other threads:[~2012-08-06 23:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-06 22:19 accessing pci_dev Paolo
2012-08-06 22:46 ` Greg KH
2012-08-06 23:16   ` Paolo [this message]
2012-08-06 23:59     ` Bjorn Helgaas
2012-08-07  0:13       ` Paolo
2012-08-07  4:18         ` Bjorn Helgaas
2012-08-07  5:34           ` Paolo

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=loom.20120807T010348-354@post.gmane.org \
    --to=paolopiace@gmail.com \
    --cc=linux-pci@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).