From: Thomas Monjalon <thomas.monjalon-pdR9zngts4EAvxtiuMwx3w@public.gmane.org>
To: "Sanford, Robert" <rsanford-JqFfY2XvxFXQT0dZR+AlfA@public.gmane.org>
Cc: dev-VfR2kkLFssw@public.gmane.org
Subject: Re: [PATCH 1/2] igb_uio: fix compability on old kernel
Date: Mon, 01 Sep 2014 13:15:57 +0200 [thread overview]
Message-ID: <1887530.KP3tPLkpR8@xps13> (raw)
In-Reply-To: <D0222750.29B5%rsanford-JqFfY2XvxFXQT0dZR+AlfA@public.gmane.org>
Hi Robert,
2014-08-26 11:08, Sanford, Robert:
> >> This is what we came up with. It works for us. In our kernel headers'
> >> linux/pci.h, pci_num_vf is enclosed within "#ifdef
> >>CONFIG_PCI_IOV/#endif";
> >> pci_intx_mask_supported and pci_check_and_mask_intx are enclosed within
> >> "#ifdef HAVE_PCI_SET_MWI/#endif".
> >>
> >> What do you think?
> >
> >Maybe we can just get rid of kernel version checks all together and
> >just use the HAVE_ checks.
> >
> >I will test on stock 2.6.32.
>
> Sorry, I spoke too soon. Although it builds with the ifdefs, I just found
> that it does not load.
> "kernel: igb_uio: Unknown symbol irq_to_desc"
Do you have some progress on this side?
Release 1.7.1 should be closed tomorrow and your help would be greatly
appreciated.
Thanks
--
Thomas
next prev parent reply other threads:[~2014-09-01 11:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-25 17:36 [PATCH 1/2] igb_uio: fix compability on old kernel Stephen Hemminger
[not found] ` <20140725103627.4ca989b7-a7a0dvSY7KrRI77zikRAJc56i+j3xesD0e7PPNI6Mm0@public.gmane.org>
2014-07-25 17:37 ` [PATCH 2/2] igb_uio: handle no IRQ fallback Stephen Hemminger
[not found] ` <20140725103754.5fbec494-a7a0dvSY7KrRI77zikRAJc56i+j3xesD0e7PPNI6Mm0@public.gmane.org>
2014-08-01 13:11 ` Thomas Monjalon
2014-08-01 13:10 ` [PATCH 1/2] igb_uio: fix compability on old kernel Thomas Monjalon
2014-08-22 17:29 ` Sanford, Robert
[not found] ` <D01CF3B4.28B5%rsanford-JqFfY2XvxFXQT0dZR+AlfA@public.gmane.org>
2014-08-22 18:09 ` Robert Sanford
[not found] ` <CA+cr1coJs9yokaDT1ya=5ChSWuSYWiF4TqmAhpcP0qLZKC4odA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-08-23 15:14 ` Stephen Hemminger
[not found] ` <20140823081453.6e3ae5d7-CA4OZQ/Yy2Lykuyl+CZolw@public.gmane.org>
2014-08-26 16:08 ` Sanford, Robert
[not found] ` <D0222750.29B5%rsanford-JqFfY2XvxFXQT0dZR+AlfA@public.gmane.org>
2014-09-01 11:15 ` Thomas Monjalon [this message]
2014-09-01 15:07 ` Guillaume Gaudonville
2014-09-01 14:55 ` Guillaume Gaudonville
[not found] ` <540488DD.3030304-pdR9zngts4EAvxtiuMwx3w@public.gmane.org>
2014-09-03 2:28 ` Thomas Monjalon
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=1887530.KP3tPLkpR8@xps13 \
--to=thomas.monjalon-pdr9zngts4eavxtiumwx3w@public.gmane.org \
--cc=dev-VfR2kkLFssw@public.gmane.org \
--cc=rsanford-JqFfY2XvxFXQT0dZR+AlfA@public.gmane.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).