DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: yang_y_yi <yang_y_yi@163.com>,
	"yangyi01@inspur.com" <yangyi01@inspur.com>
Cc: "Hu, Jiayu" <jiayu.hu@intel.com>, "dev@dpdk.org" <dev@dpdk.org>,
	olivier.matz@6wind.com, david.marchand@redhat.com,
	ferruh.yigit@intel.com
Subject: Re: [dpdk-dev] [PATCH v7 3/3] doc: update prog_guide and rel_notes for GRO
Date: Fri, 09 Oct 2020 10:45:29 +0200	[thread overview]
Message-ID: <2087326.quN09hHHGx@thomas> (raw)
In-Reply-To: <55a25def.562b.1750c69cdbb.Coremail.yang_y_yi@163.com>

09/10/2020 10:11, yang_y_yi:
> Thomas, sorry for quick reply, update for doc/guides/rel_notes/release_20_11.rst also has been there, so please ignore this one merge request.
> 
> I'm totally confused. The version Jiayu acked is v7, here are diffstat of v7 I sent, I'm not sure why these documents are updated by previous two merges. I also interdiff two merged patches and local these two patches, diff only has document changes, this is really very weird, what happened?

Listen, after several emails about this, I am a bit bored that you
don't double check before asking the same question again.
Look at the mail I sent to you originally:
	http://mails.dpdk.org/archives/dev/2020-October/184701.html*
"Applied with release notes changes integrated in the right commits"
Then I explained again:
"It has been squashed with the related code change as it should be."

It means I did what you were supposed to do:
merging the documentation updates in the commits which are doing
the code changes. So the changes are atomic with the doc,
which helps when digging in the git history.

You can see the result by yourself:
	http://git.dpdk.org/dpdk/commit/?id=1ca5e674
	http://git.dpdk.org/dpdk/commit/?id=e2d81106

While we are at it, please reply kindly to Olivier who is trying
to understand your issue with mbuf. You keep saying it is his fault
without giving the evidence he is asking for.
In short: please pay more attention to what the maintainers are saying.

Thank you


PS: please do not top-post


> diffstat 0001-gro-add-UDP-IPv4-GRO-support.patch
>  gro_udp4.c  |  433 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>  gro_udp4.h  |  281 ++++++++++++++++++++++++++++++++++++++
>  meson.build |    2
>  rte_gro.c   |   94 ++++++++++---
>  rte_gro.h   |    5
>  5 files changed, 798 insertions(+), 17 deletions(-)
> 
> diffstat 0002-gro-add-VXLAN-UDP-IPv4-GRO-support.patch
>  gro_udp4.h       |    1
>  gro_vxlan_udp4.c |  545 +++++++++++++++++++++++++++++++++++++++++++++++++++++++
>  gro_vxlan_udp4.h |  153 +++++++++++++++
>  meson.build      |    2
>  rte_gro.c        |  115 ++++++++---
>  rte_gro.h        |    3
>  6 files changed, 792 insertions(+), 27 deletions(-)
> 
> $ grep "\.rst" 0001-gro-add-UDP-IPv4-GRO-support.patch
> 
> $ grep "\.rst" 0002-gro-add-VXLAN-UDP-IPv4-GRO-support.patch
> 
> 
> At 2020-10-09 15:47:49, "yang_y_yi" <yang_y_yi@163.com> wrote:
> >Thomas, sorry for confusion, previous two merges did include changes against doc/guides/prog_guide/generic_receive_offload_lib.rst, but
> >doc/guides/rel_notes/release_20_11.rst isn't updated yet, so I posted https://patches.dpdk.org/patch/80105/ to update it, please help merge  
> >https://patches.dpdk.org/patch/80105/, thanks a lot.
> >At 2020-10-09 14:48:19, "Thomas Monjalon" <thomas@monjalon.net> wrote:
> >>09/10/2020 08:34, yang_y_yi:
> >>> Thomas, only this one of this series hasn't yet been merged, maybe you missed it, also please help merge it, thanks a lot.
> >>
> >>No I did not miss it.
> >>It has been squashed with the related code change as it should be.
> >>Please double check.
> >>
> >>[...]
> >>> >>  doc/guides/prog_guide/generic_receive_offload_lib.rst | 6 +++---
> >>> >>  doc/guides/rel_notes/release_20_11.rst                | 6 ++++++
> >>> >>  2 files changed, 9 insertions(+), 3 deletions(-)




  reply	other threads:[~2020-10-09  8:45 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-24  8:57 [dpdk-dev] [PATCH v7 0/3] gro: add UDP/IPv4 GRO and VXLAN UDP/IPv4 GRO support yang_y_yi
2020-09-24  8:57 ` [dpdk-dev] [PATCH v7 1/3] gro: add " yang_y_yi
2020-09-27  4:56   ` Hu, Jiayu
2020-09-24  8:57 ` [dpdk-dev] [PATCH v7 2/3] gro: add VXLAN " yang_y_yi
2020-09-27  1:49   ` Hu, Jiayu
2020-09-27  3:14     ` yang_y_yi
2020-09-27  5:03       ` Jiayu Hu
2020-09-27  4:56   ` Hu, Jiayu
2020-09-24  8:57 ` [dpdk-dev] [PATCH v7 3/3] doc: update prog_guide and rel_notes for GRO yang_y_yi
2020-09-27  4:56   ` Hu, Jiayu
2020-10-09  6:34     ` yang_y_yi
2020-10-09  6:48       ` Thomas Monjalon
2020-10-09  7:47         ` yang_y_yi
2020-10-09  8:00           ` Thomas Monjalon
2020-10-09  8:11           ` yang_y_yi
2020-10-09  8:45             ` Thomas Monjalon [this message]
2020-10-06 19:53 ` [dpdk-dev] [PATCH v7 0/3] gro: add UDP/IPv4 GRO and VXLAN UDP/IPv4 GRO support 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=2087326.quN09hHHGx@thomas \
    --to=thomas@monjalon.net \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=jiayu.hu@intel.com \
    --cc=olivier.matz@6wind.com \
    --cc=yang_y_yi@163.com \
    --cc=yangyi01@inspur.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).