From: malte.vesper@postgrad.manchester.ac.uk (Malte Vesper)
To: kernelnewbies@lists.kernelnewbies.org
Subject: use of dev->dev_t
Date: Tue, 17 Mar 2015 20:43:38 +0000 [thread overview]
Message-ID: <550891FA.1020007@postgrad.manchester.ac.uk> (raw)
Hi,
I am trying to write a driver that uses the MINOR(dev_t) to identify
cards. Since it is a PCI driver and I get pcidev->dev.dev_t anyway. I
thought about not bothering to store the minor number of the device.
However if I look at pcidev->dev.dev_t in the remove function (the
driver frameworks remove), I always get pcidev->dev.dev_t == 0.
Is this the intended behaviour and if so why? (This means I have to
store the minor separatly to call device_destroy())
Thanks
Malte
FYI: I am running a 3.19.0 Kernel
next reply other threads:[~2015-03-17 20:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-17 20:43 Malte Vesper [this message]
2015-03-17 21:13 ` use of dev->dev_t Greg KH
2015-03-17 21:46 ` Malte Vesper
2015-03-17 21:53 ` Greg KH
2015-03-17 22:25 ` Malte Vesper
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=550891FA.1020007@postgrad.manchester.ac.uk \
--to=malte.vesper@postgrad.manchester.ac.uk \
--cc=kernelnewbies@lists.kernelnewbies.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).