From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: David Marchand <david.marchand@6wind.com>, liljegren.mats2@gmail.com
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH 2/2] mem: fix build on 32bits system
Date: Thu, 20 Mar 2014 15:43:54 +0100 [thread overview]
Message-ID: <20222732.nJ6nn7Ydt4@xps13> (raw)
In-Reply-To: <1393575696-25289-2-git-send-email-david.marchand@6wind.com>
28/02/2014 09:21, David Marchand :
> Rebase commit 57c24af85d9eaa81549a212169605b4e2468a29f introduced a build
> regression for 32bits system.
The commit log of the rebased commit was also wrong for branch 1.6.0.
So I've reverted the rebased commit and did a new one.
It's better now.
Thank you for reporting
--
Thomas
next prev parent reply other threads:[~2014-03-20 14:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-28 8:21 [dpdk-dev] [PATCH 1/2] eal: fix use of RTE_PTR_ALIGN_CEIL macro " David Marchand
2014-02-28 8:21 ` [dpdk-dev] [PATCH 2/2] mem: fix build " David Marchand
2014-03-20 14:43 ` Thomas Monjalon [this message]
2014-03-20 14:40 ` [dpdk-dev] [PATCH 1/2] eal: fix use of RTE_PTR_ALIGN_CEIL macro " 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=20222732.nJ6nn7Ydt4@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=david.marchand@6wind.com \
--cc=dev@dpdk.org \
--cc=liljegren.mats2@gmail.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).