From: Thomas Monjalon <thomas@monjalon.net>
To: Ferruh Yigit <ferruh.yigit@intel.com>
Cc: stable@dpdk.org, dev@dpdk.org,
Jan Viktorin <viktorin@rehivetech.com>,
Jianbo Liu <jianbo.liu@arm.com>
Subject: Re: [dpdk-dev] [dpdk-stable] [PATCH] config: fix bnx2x for armv7a defconfig
Date: Mon, 06 Nov 2017 21:54:02 +0100 [thread overview]
Message-ID: <9872090.cN0LnAjKI3@xps> (raw)
In-Reply-To: <20171031173924.45370-1-ferruh.yigit@intel.com>
31/10/2017 18:39, Ferruh Yigit:
> Fixes: 02a8686263de ("mk: introduce ARMv7 architecture")
> Cc: stable@dpdk.org
>
> Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com>
> ---
> Cc: Jan Viktorin <viktorin@rehivetech.com>
> Cc: Jianbo Liu <jianbo.liu@arm.com>
> ---
> config/defconfig_arm-armv7a-linuxapp-gcc | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Applied, thanks
prev parent reply other threads:[~2017-11-06 20:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-31 17:39 [dpdk-dev] " Ferruh Yigit
2017-11-06 20:54 ` Thomas Monjalon [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=9872090.cN0LnAjKI3@xps \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=jianbo.liu@arm.com \
--cc=stable@dpdk.org \
--cc=viktorin@rehivetech.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).