From: Junyang Han <han.junyang@zte.com.cn>
To: andrew+netdev@lunn.ch
Cc: davem@davemloft.net, netdev@vger.kernel.org, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, han.junyang@zte.com.cn,
ran.ming@zte.com.cn, han.chengfei@zte.com.cn,
zhang.yanze@zte.com.cn
Subject: Re: [PATCH net-next v3 1/3] net/ethernet: add ZTE network driver support
Date: Sat, 9 May 2026 18:34:48 +0800 [thread overview]
Message-ID: <20260509103448.3263890-1-han.junyang@zte.com.cn> (raw)
In-Reply-To: <eabcb0c3-324f-4fd7-992e-8d517980ea27@lunn.ch>
[-- Attachment #1.1.1: Type: text/plain, Size: 1300 bytes --]
Hi Andrew,
Thank you for taking the time to review.
> + struct devlink *devlink;
> + int ret;
> +
> + devlink = devlink_alloc(&dh_pf_devlink_ops, sizeof(struct dh_core_dev),
> + &pdev->dev);
> Wrong indentation. In fact, this seems to have spaces not tabs. What
> does checkpatch say about these files? Or is you email still broken?
I double-checked the patch file locally. The indentation does use
tabs, not spaces:
$ cat -A v3-0001-*.patch | grep -A3 "devlink_alloc"
+^Idevlink = devlink_alloc(&dh_pf_devlink_ops, sizeof(struct dh_core_dev),$
+^I^I^I^I&pdev->dev);$
+^Iif (!devlink)$
+^I^Ireturn -ENOMEM;$
And checkpatch.pl --strict also reports 0 errors, 0 warnings:
total: 0 errors, 0 warnings, 4 checks, 320 lines checked
I checked the raw email on lore.kernel.org and found that our
corporate mail system is converting the original text/plain email
into a multipart MIME message with both text/plain and text/html
alternatives. In the HTML part, all tabs are replaced with
non-breaking spaces (HTML entity). This is likely what
you are seeing.
I will fix the mail server configuration and resend the series.
Sorry for the inconvenience, and thanks again for your patience.
Best regards,
Junyang Han
[-- Attachment #1.1.2: Type: text/html , Size: 2491 bytes --]
next prev parent reply other threads:[~2026-05-09 11:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-30 15:11 [PATCH net-next v3 0/3] Add ZTE DingHai Ethernet PF driver Junyang Han
2026-04-30 15:11 ` [PATCH net-next v3 1/3] net/ethernet: add ZTE network driver support Junyang Han
2026-04-30 19:34 ` Andrew Lunn
2026-05-09 10:34 ` Junyang Han [this message]
2026-04-30 15:11 ` [PATCH net-next v3 2/3] net/ethernet/zte/dinghai: add logging infrastructure Junyang Han
2026-04-30 19:36 ` Andrew Lunn
2026-04-30 15:11 ` [PATCH net-next v3 3/3] net/ethernet/zte/dinghai: add hardware register access and PCI capability scanning Junyang Han
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=20260509103448.3263890-1-han.junyang@zte.com.cn \
--to=han.junyang@zte.com.cn \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=han.chengfei@zte.com.cn \
--cc=kuba@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