patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Olivier Matz <olivier.matz@6wind.com>
Cc: stable@dpdk.org, dev@dpdk.org,
	"Morten Brørup" <mb@smartsharesystems.com>
Subject: Re: [dpdk-stable] [PATCH] mbuf: fix API documentation regarding VLAN flags
Date: Mon, 29 Jan 2018 17:24:29 +0100	[thread overview]
Message-ID: <5294386.SEr273L0YF@xps> (raw)
In-Reply-To: <20180129093606.18260-1-olivier.matz@6wind.com>

29/01/2018 10:36, Olivier Matz:
> Fix inconsistency between mbuf structure documentation and flags
> documentation.
> 
> Fixes: 380a7aab1ae2 ("mbuf: rename deprecated VLAN flags")
> Cc: stable@dpdk.org
> 
> Reported-by: Morten Brørup <mb@smartsharesystems.com>
> Signed-off-by: Olivier Matz <olivier.matz@6wind.com>

Applied, thanks

      reply	other threads:[~2018-01-29 16:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <98CBD80474FA8B44BF855DF32C47DC35B41D73@smartserver.smartshare.dk>
2018-01-29  9:36 ` Olivier Matz
2018-01-29 16:24   ` 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=5294386.SEr273L0YF@xps \
    --to=thomas@monjalon.net \
    --cc=dev@dpdk.org \
    --cc=mb@smartsharesystems.com \
    --cc=olivier.matz@6wind.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).