DPDK patches and discussions
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: "Habibi, Michael" <michael.f.habibi@hp.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, Aaro Koskinen <aaro.koskinen@iki.fi>
Subject: Re: [dpdk-dev] irq_to_desc undefined when compiling igb_uio
Date: Tue, 26 Aug 2014 15:32:08 -0700	[thread overview]
Message-ID: <20140826153208.290ee639@urahara> (raw)
In-Reply-To: <845ED019F5932D4E8BED0A693FDBF6E72442E9B8@G4W3304.americas.hpqcorp.net>

On Tue, 26 Aug 2014 21:43:15 +0000
"Habibi, Michael" <michael.f.habibi@hp.com> wrote:

> I agree the kernel is old but it's what we're stuck with at the moment. It
> appears that at least some thought went into this, as the code in question
> is actually compatibility code added for older kernel versions such as mine:
> 
> #if LINUX_VERSION_CODE < KERNEL_VERSION(2, 6, 37)
> /* Compatability wrapper for new kernel API for IRQ */
> #define irq_data irq_desc
> #define irq_get_irq_data(irq) irq_to_desc(irq)
> #define irq_data_get_msi(data) get_irq_desc_msi(data)
> #endif
> 
> I may just export the symbol for now. Unfortunately I'm not familiar enough
> with this area of the code, but if I end up tackling this I'll see if I can
> submit a patch if it hasn't been fixed by then.
> 
> Thanks.
> 
> P.S. Aaro sorry for the duplicate email. I resent this without my digital signature so it would get through the mailing list.

I did build test against stock 2.6.32 from upstream.
Not going to deal with all the vendor kernel issues.

      reply	other threads:[~2014-08-26 22:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-26 20:55 Habibi, Michael
2014-08-26 21:32 ` Aaro Koskinen
2014-08-26 21:43   ` Habibi, Michael
2014-08-26 22:32     ` Stephen Hemminger [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=20140826153208.290ee639@urahara \
    --to=stephen@networkplumber.org \
    --cc=aaro.koskinen@iki.fi \
    --cc=dev@dpdk.org \
    --cc=michael.f.habibi@hp.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).