From: Mateusz Berezecki <mateuszb@gmail.com>
To: Arjan van de Ven <arjan@infradead.org>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re[4]: net_device + pci_dev question
Date: Mon, 28 Nov 2005 22:08:11 +0100 [thread overview]
Message-ID: <527051512.20051128220811@gmail.com> (raw)
In-Reply-To: <1133211819.2824.82.camel@laptopd505.fenrus.org>
Hello Arjan,
On 28th november 2005 (22:03:38) you wrote:
> oh it's *your own* netdev...
Yes:-) Sorry for not being precise
> that makes things a lot easier ;)
> it's custom to have driver private data per net dev
> (see netdev_priv() to get it, alloc_etherdev() takes the size of it as
> argument). It's custom to make that private data a struct in which you
> can store the pci device pointer yourself, as well as any other per card
> data that you need to store
Ok, I will do it like that then. Thank you for the explanation on this
issue.
kind regards,
Mateusz Berezecki
prev parent reply other threads:[~2005-11-28 21:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-27 19:58 net_device + pci_dev question Mateusz Berezecki
2005-11-27 21:25 ` Arjan van de Ven
2005-11-28 20:56 ` Re[2]: " Mateusz Berezecki
2005-11-28 21:03 ` Arjan van de Ven
2005-11-28 21:08 ` Mateusz Berezecki [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=527051512.20051128220811@gmail.com \
--to=mateuszb@gmail.com \
--cc=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@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