From: Ivan Vecera <ivecera@redhat.com>
To: Christoph Hellwig <hch@infradead.org>, Petr Oros <poros@redhat.com>
Cc: netdev@vger.kernel.org, Sathya Perla <sathya.perla@broadcom.com>,
Ajit Khaparde <ajit.khaparde@broadcom.com>,
Sriharsha Basavapatna <sriharsha.basavapatna@broadcom.com>,
Somnath Kotur <somnath.kotur@broadcom.com>,
"David S. Miller" <davem@davemloft.net>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Use Kconfig flag to remove support of deprecated BE2/BE3 adapters
Date: Tue, 7 Aug 2018 13:35:18 +0200 [thread overview]
Message-ID: <e70d9925-0836-cefc-0cfe-747067c6c948@redhat.com> (raw)
In-Reply-To: <20180806162153.GA22040@infradead.org>
On 6.8.2018 18:21, Christoph Hellwig wrote:
> On Mon, Aug 06, 2018 at 02:12:28PM +0200, Petr Oros wrote:
>> Add flags to remove support of deprecated BE2/BE3 adapters.
>> BE2 disable will reduce .ko size by 2kb and BE3 by 3kb.
>> Disable both will reduce .ko size by 9kb.
>>
>> With dissabled support is also removed coresponding PCI IDs
>> and codepath with [BE2|BE3|BEx]_chip checks.
>
> deprecated seems like a really odd world for hardware.
>
> Are they just old? Did they never ship in large numbers?
>
> If you just make some cards optional why not also add options
> for families of newer cards for those who only have the older ones
> in their systems?
>
This also makes sense.
I.
next prev parent reply other threads:[~2018-08-07 11:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-06 12:12 Petr Oros
2018-08-06 13:03 ` Ivan Vecera
2018-08-06 16:21 ` Christoph Hellwig
2018-08-07 11:35 ` Ivan Vecera [this message]
2018-08-06 20:46 ` David Miller
2018-08-07 11:44 ` Ivan Vecera
2018-08-07 20:21 ` David Miller
2018-08-07 20:42 ` Ivan Vecera
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=e70d9925-0836-cefc-0cfe-747067c6c948@redhat.com \
--to=ivecera@redhat.com \
--cc=ajit.khaparde@broadcom.com \
--cc=davem@davemloft.net \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=poros@redhat.com \
--cc=sathya.perla@broadcom.com \
--cc=somnath.kotur@broadcom.com \
--cc=sriharsha.basavapatna@broadcom.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
all inboxes | Powered by JetHome®