DPDK patches and discussions
 help / color / mirror / Atom feed
From: Simon Kagstrom <simon.kagstrom@netinsight.net>
To: Thomas F Herbert <therbert@redhat.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v2] eal: Allow combining -m and --no-huge
Date: Wed, 27 May 2015 15:29:49 +0200	[thread overview]
Message-ID: <20150527152949.3e44828a@miho> (raw)
In-Reply-To: <5565C166.4090505@redhat.com>

On Wed, 27 May 2015 09:06:46 -0400
Thomas F Herbert <therbert@redhat.com> wrote:
> I just tried applying v2 of the patch to master:
> git apply ../patches/eal_common_options.patch
> error: patch failed: lib/librte_eal/common/eal_common_options.c:850
> error: lib/librte_eal/common/eal_common_options.c: patch does not apply

Hmm... I tried it myself, but just saved the email and used

  git am main.mbox

and that worked.


I´m using claws-mail as a mailer.

// Simon

  parent reply	other threads:[~2015-05-27 13:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-27  9:30 Simon Kagstrom
2015-05-27 13:06 ` Thomas F Herbert
2015-05-27 13:27   ` Mcnamara, John
2015-05-27 13:29   ` Simon Kagstrom [this message]
2015-05-27 14:17     ` Thomas F Herbert
2015-06-15 14:04 ` David Marchand
2015-06-15 14:08   ` 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=20150527152949.3e44828a@miho \
    --to=simon.kagstrom@netinsight.net \
    --cc=dev@dpdk.org \
    --cc=therbert@redhat.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).