DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: kkanas@marvell.com
Cc: dev@dpdk.org, stable@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] eal: fix spelling
Date: Sun, 07 Jul 2019 23:54:20 +0200	[thread overview]
Message-ID: <3977393.023fg09LBG@xps> (raw)
In-Reply-To: <20190604092127.25000-1-kkanas@marvell.com>

04/06/2019 11:21, kkanas@marvell.com:
> From: Krzysztof Kanas <kkanas@marvell.com>
> 
> Fixes: a753e53d517b ("eal: add device event monitor framework")
> Fixes: af75078fece3 ("first public release")
> Cc: stable@dpdk.org
> 
> Signed-off-by: Krzysztof Kanas <kkanas@marvell.com>

Applied, thanks



      parent reply	other threads:[~2019-07-07 21:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-04  9:21 kkanas
2019-06-04  9:21 ` [dpdk-dev] [PATCH] mk: fix printing target name when build completes kkanas
2019-07-30 21:35   ` Thomas Monjalon
2019-07-31  8:29     ` Bruce Richardson
2019-07-07 21: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=3977393.023fg09LBG@xps \
    --to=thomas@monjalon.net \
    --cc=dev@dpdk.org \
    --cc=kkanas@marvell.com \
    --cc=stable@dpdk.org \
    /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).