From: Simon Horman <horms@kernel.org>
To: Chu Guangqing <chuguangqing@inspur.com>
Cc: cooldavid@cooldavid.org, andrew+netdev@lunn.ch,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH for-next 1/1] net: jme: migrate to dma_map_phys instead of map_page
Date: Fri, 24 Oct 2025 18:27:39 +0100 [thread overview]
Message-ID: <aPu3C8QUYLYE8ZpG@horms.kernel.org> (raw)
In-Reply-To: <20251024070734.34353-2-chuguangqing@inspur.com>
On Fri, Oct 24, 2025 at 03:07:34PM +0800, Chu Guangqing wrote:
> After introduction of dma_map_phys(), there is no need to convert
> from physical address to struct page in order to map page. So let's
> use it directly.
>
> Signed-off-by: Chu Guangqing <chuguangqing@inspur.com>
Although there have been a number minor updates since, mainly for in-kernel
API changes, it seems to me that the last change of substance to this
driver - a feature or bug fix - was the following commit in 2016.
commit 81422e672f81 ("jme: Fix device PM wakeup API usage")
So, unless there is a tree-wide effort to move to the pattern you describe,
I am wondering if it would be better to just leave this code as-is.
Quoting documentation:
1.6.6. Clean-up patches¶
Netdev discourages patches which perform simple clean-ups, which are not in the context of other work. For example:
Addressing checkpatch.pl, and other trivial coding style warnings
Addressing Local variable ordering issues
Conversions to device-managed APIs (devm_ helpers)
This is because it is felt that the churn that such changes produce comes at a greater cost than the value of such clean-ups.
Conversely, spelling and grammar fixes are not discouraged.
https://docs.kernel.org/process/maintainer-netdev.html#clean-up-patches
next prev parent reply other threads:[~2025-10-24 17:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-24 7:07 [PATCH for-next 0/1] net: jme: migrate to dma_map_phys instead of map_page Chu Guangqing
2025-10-24 7:07 ` [PATCH for-next 1/1] " Chu Guangqing
2025-10-24 17:27 ` Simon Horman [this message]
2025-10-27 14:35 ` Leon Romanovsky
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=aPu3C8QUYLYE8ZpG@horms.kernel.org \
--to=horms@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=chuguangqing@inspur.com \
--cc=cooldavid@cooldavid.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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).