Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752205AbdI0HQG (ORCPT ); Wed, 27 Sep 2017 03:16:06 -0400 Received: from mx2.suse.de ([195.135.220.15]:58822 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1751663AbdI0HQF (ORCPT ); Wed, 27 Sep 2017 03:16:05 -0400 Message-ID: <1506496556.28482.3.camel@suse.com> Subject: Re: [PATCH V2] r8152: add Linksys USB3GIGV1 id From: Oliver Neukum To: Doug Anderson , Grant Grundler Cc: "David S . Miller" , Greg Kroah-Hartman , Hayes Wang , LKML , linux-usb , netdev@vger.kernel.org Date: Wed, 27 Sep 2017 09:15:56 +0200 In-Reply-To: References: <20170926010925.114436-1-grundler@chromium.org> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.20.5 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 680 Lines: 18 Am Dienstag, den 26.09.2017, 08:19 -0700 schrieb Doug Anderson: > > I know that for at least some of the adapters in the CDC Ethernet > blacklist it was claimed that the CDC Ethernet support in the adapter > was kinda broken anyway so the blacklist made sense. ...but for the > Linksys Gigabit adapter the CDC Ethernet driver seems to work OK, it's > just not quite as full featured / efficient as the R8152 driver. > > Is that not a concern? I guess you could tell people in this > situation that they simply need to enable the R8152 driver to get > continued support for their Ethernet adapter? Hi, yes, it is a valid concern. An #ifdef will be needed. Regards Oliver