Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S936479AbdCXQme (ORCPT ); Fri, 24 Mar 2017 12:42:34 -0400 Received: from pandora.armlinux.org.uk ([78.32.30.218]:50194 "EHLO pandora.armlinux.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S936353AbdCXQmY (ORCPT ); Fri, 24 Mar 2017 12:42:24 -0400 Date: Fri, 24 Mar 2017 16:42:02 +0000 From: Russell King - ARM Linux To: Sjoerd Simons Cc: linux-serial@vger.kernel.org, linux-renesas-soc@vger.kernel.org, Greg Kroah-Hartman , linux-kernel@vger.kernel.org, Jiri Slaby Subject: Re: [PATCH 0/2] Move uart_register_driver call to device probe for pl010 and sh-sci Message-ID: <20170324164202.GI7909@n2100.armlinux.org.uk> References: <20170324162634.8880-1-sjoerd.simons@collabora.co.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170324162634.8880-1-sjoerd.simons@collabora.co.uk> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 689 Lines: 16 On Fri, Mar 24, 2017 at 05:26:32PM +0100, Sjoerd Simons wrote: > When testing on a Renesas board with the PL010 serial driver enabled > serial output broke. Turns out the minor device numbers for both > drivers happen to overlap, causing whichever driver happened to be the > second one to register to fail. How the **** has the SH serial driver ended up with overlapping device numbers? What happened to our maintained list of allocated major/minor device numbers, which is supposed to stop crap like this happening? -- RMK's Patch system: http://www.armlinux.org.uk/developer/patches/ FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up according to speedtest.net.