DPDK patches and discussions
 help / color / mirror / Atom feed
From: Mordechay Haimovsky <motih@mellanox.com>
To: "jia.guo@intel.com" <jia.guo@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: [dpdk-dev]  [PATCH v6 1/2] eal: add uevent monitor for hot plug
Date: Wed, 13 Dec 2017 11:34:33 +0000	[thread overview]
Message-ID: <AM4PR05MB190781D7B8814134C844D9ECD2350@AM4PR05MB1907.eurprd05.prod.outlook.com> (raw)

Hello Jeff,

 I've failed to apply the patch on latest DPDK (git://dpdk.org/dpdk), 
Due to missing eal_common_vdev.c file
What am I doing wrong  ?

Moti

$ patch -p1 < dpdk-dev-v6-1-2-eal-add-uevent-monitor-for-hot-plug.patch                            
patching file drivers/bus/pci/bsd/pci.c
Hunk #1 succeeded at 126 (offset -1 lines).
patching file drivers/bus/pci/linux/pci.c
patching file drivers/bus/pci/linux/pci_init.h
patching file drivers/bus/pci/pci_common.c
Hunk #1 succeeded at 282 (offset -1 lines).
Hunk #2 succeeded at 482 (offset -1 lines).
Hunk #3 succeeded at 504 (offset -1 lines).
Hunk #4 succeeded at 568 (offset -1 lines).
patching file drivers/bus/pci/pci_common_uio.c
patching file drivers/bus/pci/private.h
patching file drivers/bus/pci/rte_bus_pci.h
patching file lib/librte_eal/bsdapp/eal/eal_dev.c
patching file lib/librte_eal/bsdapp/eal/include/exec-env/rte_dev.h
patching file lib/librte_eal/common/eal_common_bus.c
patching file lib/librte_eal/common/eal_common_dev.c
Hunk #2 succeeded at 258 (offset -10 lines).
can't find file to patch at input line 746
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/lib/librte_eal/common/eal_common_vdev.c b/lib/librte_eal/common/eal_common_vdev.c
|index f7e547a..2ad517c 100644
|--- a/lib/librte_eal/common/eal_common_vdev.c
|+++ b/lib/librte_eal/common/eal_common_vdev.c
--------------------------
File to patch: ^C

             reply	other threads:[~2017-12-13 11:34 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-13 11:34 Mordechay Haimovsky [this message]
  -- strict thread matches above, loose matches on Subject: below --
2017-09-20  4:12 [dpdk-dev] [PATCH v5 2/2] app/testpmd: use uevent to monitor hot removal Jeff Guo
2017-11-01 20:16 ` [dpdk-dev] [PATCH v6 0/2] add uevent monitor for hot plug Jeff Guo
2017-11-01 20:16   ` [dpdk-dev] [PATCH v6 1/2] eal: " Jeff Guo
2017-11-01 21:36     ` Stephen Hemminger
2017-11-01 21:41     ` Stephen Hemminger
2017-11-08  5:39       ` Guo, Jia
2017-12-25  8:30       ` Guo, Jia
2017-12-25 18:06     ` Stephen Hemminger
2018-01-02  9:40       ` Guo, Jia

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=AM4PR05MB190781D7B8814134C844D9ECD2350@AM4PR05MB1907.eurprd05.prod.outlook.com \
    --to=motih@mellanox.com \
    --cc=dev@dpdk.org \
    --cc=jia.guo@intel.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).