The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Junyang Han <han.junyang@zte.com.cn>
Cc: andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
	kuba@kernel.org, pabeni@redhat.com, horms@kernel.org,
	linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
	ran.ming@zte.com.cn, han.chengfei@zte.com.cn,
	zhang.yanze@zte.com.cn
Subject: Re: [PATCH net-next v10 0/2] Add ZTE DingHai Ethernet PF driver
Date: Thu, 06 Aug 2026 01:40:09 +0000	[thread overview]
Message-ID: <178598040988.599522.8462097247667886071.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260802160048653KdUvSUgDsEs4zwYF9Ey0q@zte.com.cn>

Hello:

This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Sun, 2 Aug 2026 16:00:48 +0800 (CST) you wrote:
> From: Junyang Han <han.junyang@zte.com.cn>
> 
> This series adds initial support for the ZTE DingHai Ethernet controller,
> a high-performance PCIe Ethernet device supporting SR-IOV, hardware
> offloading, and advanced virtualization features.
> 
> Changes from v9:
> - Makefile: remove unnecessary ccflags-y -I$(src).
> - zxdh_pf_pci_init(): dma_set_mask_and_coherent() never fails for
>   DMA_BIT_MASK(64).Just call it once.
> - zxdh_pf_probe(): reorder local variable declarations in reverse
>   xmas tree order.Don't print dev_err on devlink_alloc() failure.
> - Remove redundant initialization of fields in kzalloc'ed structs
>   (bar_chan_valid, vepa).
> - en_pf.h: drop unused includes,forward declaration of struct
>   devlink, unused enum zxdh_coredev_type, and unused struct fields
>   (bar_chan_valid, vepa, irq_lock, lock mutex, coredev_type).
> - Reply to Sashiko's review comments:
>   (1) zxdh_pf_map_capability(): validate the BAR index against
>       ZXDH_PF_MAX_BAR_VAL right after re-reading it from config space.
>   (2) zxdh_pf_map_capability(): bound-check length + offset (instead of
>       minlen + offset) against the BAR size before mapping, so the reported
>       *len never exceeds the actually mapped region and later MMIO accesses
>       cannot run past the pci_iomap_range() boundary.
>   (3) Search capabilities with IORESOURCE_MEM only (common/notify/device
>       cfg), matching the pci_request_selected_regions(IORESOURCE_MEM) call,
>       so a capability located in an I/O BAR is never mapped without having
>       been requested.
>   (4) zxdh_pf_notify_cfg_init(): rewrite
>       "if (notify_length + (notify_offset % PAGE_SIZE) <= PAGE_SIZE)" as a
>       subtraction: notify_length <= PAGE_SIZE - (notify_offset % PAGE_SIZE).
>       This removes the addition, so there is no integer wrap a
>       malicious length could exploit to bypass the check.
> 
> [...]

Here is the summary with links:
  - [net-next,v10,1/2] dinghai: add ZTE network driver support
    https://git.kernel.org/netdev/net-next/c/b8180f7977aa
  - [net-next,v10,2/2] dinghai: add hardware register access and PCI capability scanning
    (no matching commit)

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2026-08-06  1:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-02  8:00 [PATCH net-next v10 0/2] Add ZTE DingHai Ethernet PF driver han.junyang
2026-08-02  8:21 ` [PATCH net-next v10 1/2] dinghai: add ZTE network driver support han.junyang
2026-08-02  8:24 ` [PATCH net-next v10 2/2] dinghai: add hardware register access and PCI capability scanning han.junyang
2026-08-06  1:40 ` patchwork-bot+netdevbpf [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=178598040988.599522.8462097247667886071.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=han.chengfei@zte.com.cn \
    --cc=han.junyang@zte.com.cn \
    --cc=horms@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=ran.ming@zte.com.cn \
    --cc=zhang.yanze@zte.com.cn \
    /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