From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH resend] owl-linux: new package
Date: Tue, 05 Jun 2012 01:16:39 +0200 [thread overview]
Message-ID: <4FCD41D7.7010203@mind.be> (raw)
In-Reply-To: <1337980041-25675-1-git-send-email-spdawson@gmail.com>
On 05/25/12 23:07, spdawson at gmail.com wrote:
> +Kernel commit b81693d9149c598302e8eb9c20cb20330d922c8e changed the
> +net_device_ops structure, removing the ndo_set_multicast_list callback. The
> +ndo_set_rx_mode has also been added to this structure.
> +
> +The upshot of these changes is that owl-linux fails to compile with 3.3.x
> +kernels.
Won't this patch break the build on pre-3.3 kernels? I think there should
be an #if LINUX_VERSION_CODE < KERNEL_VERSION(3,3,0) around it.
Regards,
Arnout
--
Arnout Vandecappelle arnout@mind be
Senior Embedded Software Architect +32-16-286540
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
next prev parent reply other threads:[~2012-06-04 23:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-25 21:07 [Buildroot] [PATCH resend] owl-linux: new package spdawson at gmail.com
2012-06-04 23:16 ` Arnout Vandecappelle [this message]
2012-06-05 6:36 ` Simon Dawson
-- strict thread matches above, loose matches on Subject: below --
2012-06-25 19:09 spdawson at gmail.com
2012-06-26 7:35 ` Thomas Petazzoni
2012-06-26 8:07 ` Simon Dawson
2012-06-26 8:37 ` Thomas Petazzoni
2012-06-05 6:47 spdawson at gmail.com
2012-05-25 12:51 spdawson at gmail.com
2012-05-25 20:08 ` Peter Korsgaard
[not found] ` <CAC1BbcRi_0KzkKP7Pfi6e407kp3QGyiWj+mVEA355z_HeC1qvg@mail.gmail.com>
2012-05-25 20:33 ` Bernhard Reutner-Fischer
2012-05-25 21:01 ` Simon Dawson
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=4FCD41D7.7010203@mind.be \
--to=arnout@mind.be \
--cc=buildroot@busybox.net \
/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