Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754368Ab3DEFI4 (ORCPT ); Fri, 5 Apr 2013 01:08:56 -0400 Received: from nic.NetDirect.CA ([216.16.235.2]:49083 "EHLO rubicon.netdirect.ca" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750913Ab3DEFIz (ORCPT ); Fri, 5 Apr 2013 01:08:55 -0400 X-Originating-Ip: 216.16.235.2 Date: Fri, 5 Apr 2013 00:56:28 -0400 From: Chris Frey To: linux-kernel@vger.kernel.org Subject: libata: can't set force= on subdevice Message-ID: <20130405045628.GA27991@foursquare.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.2i Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 715 Lines: 25 Hi, Using kernel 3.2.x (Debian Wheezy) and when setting libata.force= kernel command line parameters, there seems to be a conflict with the '.'. For example, with the following boot argument: libata.force=ata1.0:udma/44 I get: libata: Unknown parameter '0:udma/44' libata: Unknown parameter '0:udma/44' libata: Unknown parameter '0:udma/44' libata: Unknown parameter '0:udma/44' Which I think is from kernel/params.c, not drivers/ata/libata-core.c. - Chris -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/