From: Stephen Hemminger <shemminger@osdl.org>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: "David S. Miller" <davem@davemloft.net>, netdev@oss.sgi.com
Subject: Re: [PATCH] kill ->accept_fastpath hook
Date: Wed, 9 Mar 2005 10:55:51 -0800 [thread overview]
Message-ID: <20050309105551.09a7926c@dxpl.pdx.osdl.net> (raw)
In-Reply-To: <422F44D8.3010009@pobox.com>
On Wed, 09 Mar 2005 13:47:52 -0500
Jeff Garzik <jgarzik@pobox.com> wrote:
> Stephen Hemminger wrote:
> > Trivial reordering of netdevice structure to save four bytes.
> >
> > Signed-off-by: Stephen Hemminger <shemminger@osdl.org>
>
> If we are twiddling struct net_device, might as well kill this hook.
> Never called AFAICS, and only assigned -- to a no-op stub -- in one driver.
>
> Signed-off-by: Jeff Garzik <jgarzik@pobox.com>
>
yes, kill it.
next prev parent reply other threads:[~2005-03-09 18:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-09 17:26 [PATCH] rearrange netdevice structure to save space Stephen Hemminger
2005-03-09 18:47 ` [PATCH] kill ->accept_fastpath hook Jeff Garzik
2005-03-09 18:55 ` Stephen Hemminger [this message]
2005-03-11 2:19 ` David S. Miller
2005-03-11 2:41 ` [PATCH] rearrange netdevice structure to save space David S. Miller
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=20050309105551.09a7926c@dxpl.pdx.osdl.net \
--to=shemminger@osdl.org \
--cc=davem@davemloft.net \
--cc=jgarzik@pobox.com \
--cc=netdev@oss.sgi.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