From: David Miller <davem@davemloft.net>
To: remi.denis-courmont@nokia.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH 3/3] Phonet: declare headers
Date: Wed, 01 Oct 2008 01:32:13 -0700 (PDT) [thread overview]
Message-ID: <20081001.013213.193713776.davem@davemloft.net> (raw)
In-Reply-To: <200810011054.52951.remi.denis-courmont@nokia.com>
From: "Rémi Denis-Courmont" <remi.denis-courmont@nokia.com>
Date: Wed, 1 Oct 2008 10:54:52 +0300
> While we're on if_phonet.h, I also wonder what the "right" place for
> phonet_header_ops is... Currently in phonet.ko, any network device driver
> link-depends on the socket stack :-( for two tiny little header_ops
> callbacks. Is that OK? or should it go to core like the Ethernet ops, or be
> inline'd?
The drivers are kind of useless without the socket layer
so it doesn't seem so awful to have this dependency.
prev parent reply other threads:[~2008-10-01 8:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-24 16:11 [PATCH 3/3] Phonet: declare headers Remi Denis-Courmont
2008-09-30 9:59 ` David Miller
2008-10-01 7:54 ` Rémi Denis-Courmont
2008-10-01 7:57 ` [PATCH] Protect if_phonet.h against multiple inclusions Remi Denis-Courmont
2008-10-01 8:32 ` David Miller
2008-10-01 8:32 ` David Miller [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=20081001.013213.193713776.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=remi.denis-courmont@nokia.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).