DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: "Min Hu (Connor)" <humin29@huawei.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Some questions about web site: git.dpdk.org
Date: Mon, 11 Jan 2021 12:02:41 +0000
Message-ID: <305eb91d-8e4e-f0be-8274-02dbe9a014fa@intel.com> (raw)
In-Reply-To: <3add3307-1f7d-282c-15d1-0dc70876845a@huawei.com>

On 1/9/2021 10:36 AM, Min Hu (Connor) wrote:
> Hello, Ferruh and all,
>      I find a bug: some patches which have already been merged into
> the origin/main branch, but I cannot find them in the archive path?:
>      https://git.dpdk.org/dpdk/log/

Hi Connor,

They are still in the sub-tree (next-net) and not merged to the main repo. They 
will be in the main repo after Thomas/David pulls them.

Currently you can see them in the next-net repo:

Following commits can be found at:

> For example,like these patches:
> commit 3c92077bba1a8991ca656d81beca5c80dbf7a6f7
> Author: Lijun Ou <oulijun@huawei.com>
> Date:   Thu Dec 10 20:48:42 2020 +0800
>      net/hns3: adjust printing MAC addresses in log
>      Here the printing of MAC addresses is adjusted. After the
>      modification, only some bytes of the MAC address are
>      displayed.
>      Signed-off-by: Chengchang Tang <tangchengchang@huawei.com>
>      Signed-off-by: Lijun Ou <oulijun@huawei.com>
> commit 9883e29d3b65123b373ade1e4800b32a475cac15
> Author: Min Hu (Connor) <humin29@huawei.com>
> Date:   Thu Dec 10 20:48:43 2020 +0800
>      net/hns3: fix FEC state query
>      As FEC is not supported below 10 Gbps,
>      CMD(HNS3_OPC_CONFIG_FEC_MODE) offered from
>      Firmware read will return fail in 10 Gbps device.
>      This patch will prevent read this CMD when below 10 Gbps,
>      as this is non-sense.
>      Fixes: 9bf2ea8dbc65 ("net/hns3: support FEC")
>      Cc: stable@dpdk.org
>      Signed-off-by: Min Hu (Connor) <humin29@huawei.com>
>      Signed-off-by: Lijun Ou <oulijun@huawei.com>
> By the way, is there any other archive path storing pathes which we can refer to?
>      Thanks.
>                      by Connor

      reply	other threads:[~2021-01-11 12:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-09 10:36 Min Hu (Connor)
2021-01-11 12:02 ` Ferruh Yigit [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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=305eb91d-8e4e-f0be-8274-02dbe9a014fa@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=dev@dpdk.org \
    --cc=humin29@huawei.com \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

DPDK patches and discussions

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://inbox.dpdk.org/dev/0 dev/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 dev dev/ https://inbox.dpdk.org/dev \
	public-inbox-index dev

Example config snippet for mirrors.
Newsgroup available over NNTP:

AGPL code for this site: git clone https://public-inbox.org/public-inbox.git