From: Andrew Lunn <andrew@lunn.ch>
To: "Dr. David Alan Gilbert" <linux@treblig.org>
Cc: ecree.xilinx@gmail.com, habetsm.xilinx@gmail.com,
andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, netdev@vger.kernel.org,
linux-net-drivers@amd.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next] sfc: Remove deadcode
Date: Sat, 2 Nov 2024 18:09:26 +0100 [thread overview]
Message-ID: <fd699a8a-d595-4e7d-8d6d-fd5da1f8ce3b@lunn.ch> (raw)
In-Reply-To: <ZyY_avQn4yuj6WC3@gallifrey>
On Sat, Nov 02, 2024 at 03:04:10PM +0000, Dr. David Alan Gilbert wrote:
> * linux@treblig.org (linux@treblig.org) wrote:
> > From: "Dr. David Alan Gilbert" <linux@treblig.org>
> >
> > ef4_farch_dimension_resources(), ef4_nic_fix_nodesc_drop_stat(),
> > ef4_ticks_to_usecs() and ef4_tx_get_copy_buffer_limited() were
> > copied over from efx_ equivalents in 2016 but never used by
> > commit 5a6681e22c14 ("sfc: separate out SFC4000 ("Falcon") support into new
> > sfc-falcon driver")
> >
> > EF4_MAX_FLUSH_TIME is also unused.
> >
> > Remove them.
> >
> > Signed-off-by: Dr. David Alan Gilbert <linux@treblig.org>
>
> Actually, NAK this copy; I'll resend it in a minute
> as part of a series with a whole load more.
https://www.kernel.org/doc/html/latest/process/maintainer-netdev.html#updating-patch-status
pw-bot: changes-requested
As a result the bot will set the entire series to Changes
Requested. This may be useful when author discovers a bug in their
own series and wants to prevent it from getting applied.
Andrew
---
pw-bot: cr
prev parent reply other threads:[~2024-11-02 17:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-02 14:33 [PATCH net-next] sfc: Remove deadcode linux
2024-11-02 15:04 ` Dr. David Alan Gilbert
2024-11-02 17:09 ` Andrew Lunn [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=fd699a8a-d595-4e7d-8d6d-fd5da1f8ce3b@lunn.ch \
--to=andrew@lunn.ch \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=ecree.xilinx@gmail.com \
--cc=edumazet@google.com \
--cc=habetsm.xilinx@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net-drivers@amd.com \
--cc=linux@treblig.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