From: "Wu, Jingjing" <jingjing.wu@intel.com>
To: "Guo, Jia" <jia.guo@intel.com>,
"Yigit, Ferruh" <ferruh.yigit@intel.com>,
"Tan, Jianfeng" <jianfeng.tan@intel.com>
Cc: "thomas@monjalon.net" <thomas@monjalon.net>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] igb_uio: fix uevent montior issue
Date: Wed, 31 Jan 2018 02:15:03 +0000 [thread overview]
Message-ID: <9BB6961774997848B5B42BEC655768F810F3BF4C@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <1517306475-2153-1-git-send-email-jia.guo@intel.com>
> -----Original Message-----
> From: Guo, Jia
> Sent: Tuesday, January 30, 2018 6:01 PM
> To: Yigit, Ferruh <ferruh.yigit@intel.com>; Wu, Jingjing <jingjing.wu@intel.com>; Tan,
> Jianfeng <jianfeng.tan@intel.com>
> Cc: thomas@monjalon.net; dev@dpdk.org; Guo, Jia <jia.guo@intel.com>
> Subject: [PATCH] igb_uio: fix uevent montior issue
>
> udev could not detect remove and add event of device when hotplug in
> and out devices, that related with the fix about using pointer of
> rte_uio_pci_dev as dev_id instead of uio_device for irq device handler,
> that would result igb uio irq failure when kernel version after than 3.17.
> so this patch correct it by use kernel version check before handle the
> pci interrupt.
>
> Fixes: 6b9ed026a870 ("igb_uio: fix build with kernel <= 3.17")
> Signed-off-by: Jeff Guo <jia.guo@intel.com>
Reviewed-by: Jingjing Wu <jingjing.wu@intel.com>
next prev parent reply other threads:[~2018-01-31 2:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-30 10:01 Jeff Guo
2018-01-31 2:15 ` Wu, Jingjing [this message]
2018-02-08 22:01 ` Thomas Monjalon
2018-02-12 8:28 ` Guo, Jia
2018-02-12 9:46 ` Thomas Monjalon
2018-02-13 9:32 ` Ferruh Yigit
2018-02-27 6:17 ` Guo, Jia
2018-02-27 7:20 ` [dpdk-dev] [PATCH V2] " Jeff Guo
2018-03-26 18:28 ` Ferruh Yigit
2018-03-27 7:46 ` Guo, Jia
2018-03-27 17:10 ` Ferruh Yigit
-- strict thread matches above, loose matches on Subject: below --
2018-01-30 9:55 [dpdk-dev] [PATCH] " Jeff Guo
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=9BB6961774997848B5B42BEC655768F810F3BF4C@SHSMSX103.ccr.corp.intel.com \
--to=jingjing.wu@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=jia.guo@intel.com \
--cc=jianfeng.tan@intel.com \
--cc=thomas@monjalon.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;
as well as URLs for NNTP newsgroup(s).