From: David Miller <davem@davemloft.net>
To: skhan@linuxfoundation.org
Cc: gnomes@lxorguk.ukuu.org.uk, puranjay12@gmail.com,
bjorn@helgaas.com, stephen@networkplumber.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-kernel-mentees@lists.linuxfoundation.org,
linux-pci@vger.kernel.org
Subject: Re: [PATCH v3 0/3] net: fddi: skfp: Use PCI generic definitions instead of private duplicates
Date: Wed, 26 Jun 2019 13:03:48 -0700 (PDT) [thread overview]
Message-ID: <20190626.130348.743645536748522991.davem@davemloft.net> (raw)
In-Reply-To: <5f04f52d-8911-4db9-4321-00334d357d54@linuxfoundation.org>
From: Shuah Khan <skhan@linuxfoundation.org>
Date: Fri, 21 Jun 2019 10:36:02 -0600
> Stephen Hemminger is suggesting removal as well. Makes sense to me.
...
> What would you recommend the next steps are? Would like driver
> removed?
If you hadn't proposed the cleanups nobody would have said to remove
this driver. Really if someone wants to go through the tree and
send removal patches for seemingly really unused drivers, that is
a separate piece of work unrelated to your cleanup.
While something still is in the tree we should clean it up from
stuff like this.
Therefore, I'll be applying v5 of your changes, thanks.
next prev parent reply other threads:[~2019-06-26 20:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-21 9:46 [PATCH v3 0/3] net: fddi: skfp: Use PCI generic definitions instead of private duplicates Puranjay Mohan
2019-06-21 9:46 ` [PATCH v3 1/3] net: fddi: skfp: Rename local PCI defines to match generic PCI defines Puranjay Mohan
2019-06-21 9:46 ` [PATCH v3 2/3] net: fddi: skfp: Include generic PCI definitions Puranjay Mohan
2019-06-21 9:46 ` [PATCH v3 3/3] net: fddi: skfp: Remove unused private " Puranjay Mohan
2019-06-21 14:05 ` [PATCH v3 0/3] net: fddi: skfp: Use PCI generic definitions instead of private duplicates Bjorn Helgaas
2019-06-21 15:20 ` Alan Cox
2019-06-21 16:36 ` Shuah Khan
2019-06-26 20:03 ` David Miller [this message]
2019-06-21 16:44 ` Bjorn Helgaas
2019-06-21 17:59 ` Joe Perches
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=20190626.130348.743645536748522991.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=bjorn@helgaas.com \
--cc=gnomes@lxorguk.ukuu.org.uk \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=puranjay12@gmail.com \
--cc=skhan@linuxfoundation.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;
as well as URLs for NNTP newsgroup(s).