From mboxrd@z Thu Jan 1 00:00:00 1970 From: Johannes Berg Subject: Re: [PATCH] Driver-core: Fix bluetooth network device rename regression Date: Thu, 22 Jul 2010 20:20:28 +0200 Message-ID: <1279822828.12439.24.camel@jlt3.sipsolutions.net> References: <20100621222938.GA20583@suse.de> <20100621231058.GA1066@suse.de> <20100622035631.GA3755@suse.de> <20100708211930.GA15385@kroah.com> <20100708230601.GB17002@kroah.com> <20100719133451.0862ca62.akpm@linux-foundation.org> <20100720201334.GA11991@suse.de> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Cc: "Eric W. Biederman" , Greg KH , Andrew Morton , Greg KH , "Rafael J. Wysocki" , "Maciej W. Rozycki" , netdev To: Kay Sievers Return-path: Received: from he.sipsolutions.net ([78.46.109.217]:55412 "EHLO sipsolutions.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751772Ab0GVSVR (ORCPT ); Thu, 22 Jul 2010 14:21:17 -0400 In-Reply-To: Sender: netdev-owner@vger.kernel.org List-ID: On Thu, 2010-07-22 at 19:44 +0200, Kay Sievers wrote: > Yes. The drivers are broken in its core use pattern, and enabling a > (non-common) new feature exposes this. You've been saying this for a long time now, but I still don't buy it. This stuff WORKED before. Now, years later, you're saying that it has a broken use pattern, and needs to be fixed. That's a pipe dream. In the real world, you can't deliberately break things because years later you decide that the use pattern that was working fine before is broken. johannes