From: Zijun Hu <zijun_hu@icloud.com>
To: Paolo Abeni <pabeni@redhat.com>, Timur Tabi <timur@kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
Zijun Hu <quic_zijuhu@quicinc.com>
Subject: Re: [PATCH net-next v5] net: qcom/emac: Find sgmii_ops by device_for_each_child()
Date: Thu, 19 Sep 2024 19:27:00 +0800 [thread overview]
Message-ID: <f70ca3a8-2fe8-404c-8ead-7e7bc5417f52@icloud.com> (raw)
In-Reply-To: <9b668881-b933-4bae-a0da-a107d2b531e9@redhat.com>
On 2024/9/19 16:26, Paolo Abeni wrote:
> On 9/17/24 03:57, Zijun Hu wrote:
>> From: Zijun Hu <quic_zijuhu@quicinc.com>
>>
>> To prepare for constifying the following old driver core API:
>>
>> struct device *device_find_child(struct device *dev, void *data,
>> int (*match)(struct device *dev, void *data));
>> to new:
>> struct device *device_find_child(struct device *dev, const void *data,
>> int (*match)(struct device *dev, const void *data));
>>
>> The new API does not allow its match function (*match)() to modify
>> caller's match data @*data, but emac_sgmii_acpi_match(), as the old
>> API's match function, indeed modifies relevant match data, so it is
>> not suitable for the new API any more, solved by implementing the same
>> finding sgmii_ops function by correcting the function and using it
>> as parameter of device_for_each_child() instead of device_find_child().
>>
>> By the way, this commit does not change any existing logic.
>>
>> Signed-off-by: Zijun Hu <quic_zijuhu@quicinc.com>
>
>
> ## Form letter - net-next-closed
>
> The merge window for v6.12 and therefore net-next is closed for new
> drivers, features, code refactoring and optimizations. We are currently
> accepting bug fixes only.
>
> Please repost when net-next reopens after Sept 30th.
>
> RFC patches sent for review only are obviously welcome at any time.
>
thanks for your remainder. will post it after merge window is opened again.
and always welcome code reviewers to give comments before that.
(^^).
> See:
> https://www.kernel.org/doc/html/next/process/maintainer-netdev.html#development-cycle
prev parent reply other threads:[~2024-09-19 11:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-17 1:57 Zijun Hu
2024-09-19 8:26 ` Paolo Abeni
2024-09-19 11:27 ` Zijun Hu [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=f70ca3a8-2fe8-404c-8ead-7e7bc5417f52@icloud.com \
--to=zijun_hu@icloud.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=quic_zijuhu@quicinc.com \
--cc=timur@kernel.org \
/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
all inboxes | Powered by JetHome®