From: Simon Horman <horms@kernel.org>
To: Yue Haibing <yuehaibing@huawei.com>
Cc: przemyslaw.kitszel@intel.com, linux-kernel@vger.kernel.org,
edumazet@google.com, netdev@vger.kernel.org,
anthony.l.nguyen@intel.com, intel-wired-lan@lists.osuosl.org,
olga.zaborska@intel.com, kuba@kernel.org, pabeni@redhat.com,
davem@davemloft.net
Subject: Re: [Intel-wired-lan] [PATCH net-next] igbvf: Remove two unused declarations
Date: Fri, 16 Aug 2024 17:51:24 +0100 [thread overview]
Message-ID: <20240816165124.GZ632411@kernel.org> (raw)
In-Reply-To: <20240816101638.882072-1-yuehaibing@huawei.com>
On Fri, Aug 16, 2024 at 06:16:38PM +0800, Yue Haibing wrote:
> There is no caller and implementations in tree.
>
> Signed-off-by: Yue Haibing <yuehaibing@huawei.com>
Reviewed-by: Simon Horman <horms@kernel.org>
WARNING: multiple messages have this Message-ID (diff)
From: Simon Horman <horms@kernel.org>
To: Yue Haibing <yuehaibing@huawei.com>
Cc: anthony.l.nguyen@intel.com, przemyslaw.kitszel@intel.com,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, olga.zaborska@intel.com,
intel-wired-lan@lists.osuosl.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next] igbvf: Remove two unused declarations
Date: Fri, 16 Aug 2024 17:51:24 +0100 [thread overview]
Message-ID: <20240816165124.GZ632411@kernel.org> (raw)
In-Reply-To: <20240816101638.882072-1-yuehaibing@huawei.com>
On Fri, Aug 16, 2024 at 06:16:38PM +0800, Yue Haibing wrote:
> There is no caller and implementations in tree.
>
> Signed-off-by: Yue Haibing <yuehaibing@huawei.com>
Reviewed-by: Simon Horman <horms@kernel.org>
next prev parent reply other threads:[~2024-08-16 16:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-16 10:16 [Intel-wired-lan] [PATCH net-next] igbvf: Remove two unused declarations Yue Haibing
2024-08-16 10:16 ` Yue Haibing
2024-08-16 16:51 ` Simon Horman [this message]
2024-08-16 16:51 ` Simon Horman
2024-08-20 1:00 ` [Intel-wired-lan] " patchwork-bot+netdevbpf
2024-08-20 1:00 ` 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=20240816165124.GZ632411@kernel.org \
--to=horms@kernel.org \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=olga.zaborska@intel.com \
--cc=pabeni@redhat.com \
--cc=przemyslaw.kitszel@intel.com \
--cc=yuehaibing@huawei.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.