From: Stephen Hemminger <shemminger@vyatta.com>
To: Krzysztof Halasa <khc@pm.waw.pl>
Cc: David Miller <davem@davemloft.net>, netdev@vger.kernel.org
Subject: Re: [PATCH] hdlc: fix compile problem
Date: Wed, 7 Jan 2009 15:28:58 -0800 [thread overview]
Message-ID: <20090107152858.6fb8ac5d@extreme> (raw)
In-Reply-To: <m3d4eyvh28.fsf@maximus.localdomain>
On Thu, 08 Jan 2009 00:21:03 +0100
Krzysztof Halasa <khc@pm.waw.pl> wrote:
> Stephen Hemminger <shemminger@vyatta.com> writes:
>
> > Fix build problem with hdlc driver. hdlc_null_ops was being referenced
> > before it was defined!
>
> :-)
>
> Unfortunately I can't see it, which tree is it?
>
>
> In David's and Linus' trees it appears twice, it seem to be entirely
> correct and btw you are the author :-)
> ... and it compiled here 100 times or so :-)
>
> static const struct header_ops hdlc_null_ops;
> ^^^^^^^^^^^^^
> static void hdlc_setup_dev(struct net_device *dev)
> {
> /* Re-init all variables changed by HDLC protocol drivers,
> * including ether_setup() called from hdlc_raw_eth.c.
> */
> dev->get_stats = hdlc_get_stats;
> dev->flags = IFF_POINTOPOINT | IFF_NOARP;
> dev->mtu = HDLC_MAX_MTU;
> dev->type = ARPHRD_RAWHDLC;
> dev->hard_header_len = 16;
> dev->addr_len = 0;
> dev->header_ops = &hdlc_null_ops;
> ^^^^^^^^^^^^^^^^
> dev->change_mtu = hdlc_change_mtu;
> }
It was introduced (by me) in previous patch. Since that isn't applied yet,
I'll go back and fix.
next prev parent reply other threads:[~2009-01-07 23:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-07 22:13 [PATCH] hdlc: fix compile problem Stephen Hemminger
2009-01-07 23:21 ` Krzysztof Halasa
2009-01-07 23:28 ` Stephen Hemminger [this message]
2009-01-08 1:00 ` Krzysztof Halasa
2009-01-08 1:08 ` Stephen Hemminger
2009-01-08 1:26 ` Krzysztof Halasa
2009-01-08 2:13 ` David Miller
2009-01-08 15:40 ` Krzysztof Halasa
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=20090107152858.6fb8ac5d@extreme \
--to=shemminger@vyatta.com \
--cc=davem@davemloft.net \
--cc=khc@pm.waw.pl \
--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;
as well as URLs for NNTP newsgroup(s).