Netdev List
 help / color / mirror / Atom feed
From: "Vincenzo Palazzo" <vincenzopalazzodev@gmail.com>
To: "Stephen Hemminger" <stephen@networkplumber.org>
Cc: <netdev@vger.kernel.org>, <davem@davemloft.net>
Subject: Re: [PATCH v1] netdevice: clean old FIXME that it is not worthed
Date: Mon, 06 Mar 2023 17:55:29 +0100	[thread overview]
Message-ID: <CQZGI7VY8XBX.3B5BUMEK4V9L1@vincent-arch> (raw)
In-Reply-To: <20230304121732.3d102b7e@hermes.local>

On Sat Mar 4, 2023 at 9:17 PM CET, Stephen Hemminger wrote:
> On Sat,  4 Mar 2023 20:44:33 +0100
> Vincenzo Palazzo <vincenzopalazzodev@gmail.com> wrote:
>
> > Alternative patch that removes an old FIXME because it currently
> > the change is worthed as some comments in the patch point out
> > (https://lore.kernel.org/all/20230304080650.74e8d396@hermes.local/#t)
> > 
> > Signed-off-by: Vincenzo Palazzo <vincenzopalazzodev@gmail.com>
> > ---
> >  include/linux/netdevice.h | 1 -
> >  1 file changed, 1 deletion(-)
> > 
> > diff --git a/include/linux/netdevice.h b/include/linux/netdevice.h
> > index 6a14b7b11766..82af7eb62075 100644
> > --- a/include/linux/netdevice.h
> > +++ b/include/linux/netdevice.h
> > @@ -2033,7 +2033,6 @@ struct net_device {
> >  	struct dev_ifalias	__rcu *ifalias;
> >  	/*
> >  	 *	I/O specific fields
> > -	 *	FIXME: Merge these and struct ifmap into one
> >  	 */
> >  	unsigned long		mem_end;
> >  	unsigned long		mem_start;
>
> These fields actually are only used by old hardware devices that
> pre-date buses with auto discovery. I.e ISA bus not PCI.
>
> Since ISA bus support is gone, either these devices should have
> been removed as well or they really aren't using those fields..
>
> If someone wanted to clean this stuff out, start by seeing
> if any of those devices still live. For example, the E1000e has
> a couple of variants and dropping support for the non-PCI variant
> would be ok.
>
> All of arcnet could/should go away? Maybe move to staging?
>
> The wan devices might also have been ISA only devices that are now
> unusable.

Well I could do this, also because from the patch [1] that I made
looks like there are not a lot of driver that are using these fields.

However, what is the right process for this kind of clean up work?

[1] https://lore.kernel.org/all/20230304122432.265902-1-vincenzopalazzodev@gmail.com/

      reply	other threads:[~2023-03-06 16:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-04 19:44 [PATCH v1] netdevice: clean old FIXME that it is not worthed Vincenzo Palazzo
2023-03-04 20:17 ` Stephen Hemminger
2023-03-06 16:55   ` Vincenzo Palazzo [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=CQZGI7VY8XBX.3B5BUMEK4V9L1@vincent-arch \
    --to=vincenzopalazzodev@gmail.com \
    --cc=davem@davemloft.net \
    --cc=netdev@vger.kernel.org \
    --cc=stephen@networkplumber.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