From: Jesper Dangaard Brouer <hawk@comx.dk>
To: David Miller <davem@davemloft.net>
Cc: paul.gortmaker@windriver.com, eric.dumazet@gmail.com,
netdev@vger.kernel.org, sfr@canb.auug.org.au
Subject: Re: [PATCH net-next] net: flow_dissector.c missing include linux/export.h
Date: Tue, 24 Jan 2012 22:42:44 +0100 [thread overview]
Message-ID: <1327441364.2721.23.camel@probook> (raw)
In-Reply-To: <20120124.155135.1784877918701583546.davem@davemloft.net>
On Tue, 2012-01-24 at 15:51 -0500, David Miller wrote:
> Jesper did you actually hit this problem and get a real build
> failure?
Yes, but I didn't explain the circumstances, sorry.
I was backporting Erics SFQ bug fix (sch_sfq: dont put new flow at the
end of flows / d47a0ac7b66) to stable kernel 3.2.1.
But to avoid conflicts I also cherry-picked the other SFQ changes, plus
the skb_flow_dissect changes, and cherry-picked:
# sch_sfq: use skb_flow_dissect()
# (Need flow_dissect APIs)
git cherry-pick 11fca931d35a34d01ce209eb8d51ff667c9f5e7c
# net: introduce skb_flow_dissect()
git cherry-pick 0744dd00c1b1be99a25b62b1b48df440e82e57e0
# flow_dissector: use a 64bit load/store
git cherry-pick 4d77d2b567ec66a443792d99e96ac760991d80d0
# sch_sfq: rehash queues in perturb timer
git cherry-pick 225d9b89c937633dfeec502741a174fe0bab5b9f
# sch_sfq: dont put new flow at the end of flows
git cherry-pick d47a0ac7b66883987275598d6039f902f4410ca9
# net_sched: sfq: fix mem alloc error recovery
git cherry-pick bd16a6cce2a7f169b559abc5672fd2c66e91fb36
So, I guess the "problem" is because I didn't have the patch, which adds
the include net/netprio_cgroup.h in linux/netdevice.h, and have the side
effect of including module.h, the patch:
net: add network priority cgroup infrastructure (v4) / 5bc1421e34ecfe
git describe --contains 5bc1421e34ecfe
v3.3-rc1~182^2~519
Still think it more correct to include linux/export.h in
flow_dissector.c.
--
Best regards,
Jesper Dangaard Brouer
ComX Networks A/S
Linux Network Kernel Developer
Cand. Scient Datalog / MSc.CS
Author of http://www.iptv-analyzer.org
LinkedIn: http://www.linkedin.com/in/brouer
prev parent reply other threads:[~2012-01-24 21:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-24 15:57 [PATCH net-next] net: flow_dissector.c missing include linux/export.h Jesper Dangaard Brouer
2012-01-24 16:15 ` Eric Dumazet
2012-01-24 19:44 ` Paul Gortmaker
2012-01-24 20:51 ` David Miller
2012-01-24 20:59 ` Paul Gortmaker
2012-01-24 21:03 ` David Miller
2012-01-24 21:42 ` Jesper Dangaard Brouer [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=1327441364.2721.23.camel@probook \
--to=hawk@comx.dk \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=paul.gortmaker@windriver.com \
--cc=sfr@canb.auug.org.au \
/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).