From: Krzysztof Halasa <khc@pm.waw.pl>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org, vinay@linux.vnet.ibm.com,
krkumar2@in.ibm.com, mchan@broadcom.com, Matheos.Worku@Sun.COM,
linux-wireless@vger.kernel.org
Subject: Re: [PATCH 26/39]: netdev: netdev_priv() can now be sane again.
Date: Thu, 03 Jul 2008 16:18:21 +0200 [thread overview]
Message-ID: <m3d4lvnj9u.fsf@maximus.localdomain> (raw)
In-Reply-To: <20080703.042614.244608628.davem@davemloft.net> (David Miller's message of "Thu\, 03 Jul 2008 04\:26\:14 -0700 \(PDT\)")
David Miller <davem@davemloft.net> writes:
> If all drivers call netdev_priv(), there is no confusion :)
>
> I plan to rename dev->priv to dev->_priv and fix all the fallout.
Do you mean practically deleting dev->priv? That would make sense.
--
Krzysztof Halasa
next prev parent reply other threads:[~2008-07-03 14:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-03 7:04 [PATCH 26/39]: netdev: netdev_priv() can now be sane again David Miller
2008-07-03 11:23 ` Krzysztof Halasa
2008-07-03 11:26 ` David Miller
2008-07-03 14:18 ` Krzysztof Halasa [this message]
2008-07-03 22:55 ` David Miller
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=m3d4lvnj9u.fsf@maximus.localdomain \
--to=khc@pm.waw.pl \
--cc=Matheos.Worku@Sun.COM \
--cc=davem@davemloft.net \
--cc=krkumar2@in.ibm.com \
--cc=linux-wireless@vger.kernel.org \
--cc=mchan@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=vinay@linux.vnet.ibm.com \
/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).