From: patchwork-bot+netdevbpf@kernel.org
To: Gaosheng Cui <cuigaosheng1@huawei.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
edumazet@google.com, vbordug@ru.mvista.com, kuba@kernel.org,
pabeni@redhat.com, linuxppc-dev@lists.ozlabs.org,
davem@davemloft.net
Subject: Re: [PATCH] net: ethernet: remove fs_mii_disconnect and fs_mii_connect declarations
Date: Mon, 19 Sep 2022 21:20:14 +0000 [thread overview]
Message-ID: <166362241432.4330.4829794093210572810.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220909062959.1144493-1-cuigaosheng1@huawei.com>
Hello:
This patch was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Fri, 9 Sep 2022 14:29:59 +0800 you wrote:
> fs_mii_disconnect and fs_mii_connect have been removed since
> commit 5b4b8454344a ("[PATCH] FS_ENET: use PAL for mii management"),
> so remove them.
>
> Signed-off-by: Gaosheng Cui <cuigaosheng1@huawei.com>
> ---
> drivers/net/ethernet/freescale/fs_enet/fs_enet-main.c | 3 ---
> 1 file changed, 3 deletions(-)
Here is the summary with links:
- net: ethernet: remove fs_mii_disconnect and fs_mii_connect declarations
https://git.kernel.org/netdev/net-next/c/feceb24ed79a
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
WARNING: multiple messages have this Message-ID (diff)
From: patchwork-bot+netdevbpf@kernel.org
To: Gaosheng Cui <cuigaosheng1@huawei.com>
Cc: pantelis.antoniou@gmail.com, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
vbordug@ru.mvista.com, linuxppc-dev@lists.ozlabs.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] net: ethernet: remove fs_mii_disconnect and fs_mii_connect declarations
Date: Mon, 19 Sep 2022 21:20:14 +0000 [thread overview]
Message-ID: <166362241432.4330.4829794093210572810.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220909062959.1144493-1-cuigaosheng1@huawei.com>
Hello:
This patch was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Fri, 9 Sep 2022 14:29:59 +0800 you wrote:
> fs_mii_disconnect and fs_mii_connect have been removed since
> commit 5b4b8454344a ("[PATCH] FS_ENET: use PAL for mii management"),
> so remove them.
>
> Signed-off-by: Gaosheng Cui <cuigaosheng1@huawei.com>
> ---
> drivers/net/ethernet/freescale/fs_enet/fs_enet-main.c | 3 ---
> 1 file changed, 3 deletions(-)
Here is the summary with links:
- net: ethernet: remove fs_mii_disconnect and fs_mii_connect declarations
https://git.kernel.org/netdev/net-next/c/feceb24ed79a
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2022-09-19 21:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-09 6:29 [PATCH] net: ethernet: remove fs_mii_disconnect and fs_mii_connect declarations Gaosheng Cui
2022-09-09 6:29 ` Gaosheng Cui
2022-09-12 22:24 ` Andrew Lunn
2022-09-12 22:24 ` Andrew Lunn
2022-09-19 21:20 ` patchwork-bot+netdevbpf [this message]
2022-09-19 21:20 ` patchwork-bot+netdevbpf
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=166362241432.4330.4829794093210572810.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=cuigaosheng1@huawei.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=vbordug@ru.mvista.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.