Return-Path: From: Ilya Faenson To: Guenter Roeck , Marcel Holtmann CC: "linux-kernel@vger.kernel.org" , "Frederic Danis" , BlueZ development , "linux-serial@vger.kernel.org" Subject: RE: Build error -in -next due to 'Bluetooth: hci_uart: Support operational speed during setup' Date: Mon, 15 Jun 2015 14:38:45 +0000 Message-ID: References: <557ED81D.7090908@roeck-us.net> <7CF3D545-DAE4-4510-9726-5D40740DDC5D@holtmann.org> <557EE045.2090503@roeck-us.net> In-Reply-To: <557EE045.2090503@roeck-us.net> Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 List-ID: Hi Guenter, -----Original Message----- From: linux-bluetooth-owner@vger.kernel.org [mailto:linux-bluetooth-owner@v= ger.kernel.org] On Behalf Of Guenter Roeck Sent: Monday, June 15, 2015 10:25 AM To: Marcel Holtmann Cc: linux-kernel@vger.kernel.org; Frederic Danis; BlueZ development; linux-= serial@vger.kernel.org Subject: Re: Build error -in -next due to 'Bluetooth: hci_uart: Support ope= rational speed during setup' On 06/15/2015 06:58 AM, Marcel Holtmann wrote: > Hi Guenter, > >> alpha:allmodconfig fails to build in -next with >> >> drivers/bluetooth/hci_ldisc.c: In function 'hci_uart_set_baudrate': >> drivers/bluetooth/hci_ldisc.c:276:22: error: 'BOTHER' undeclared >> >> BOTHER is not defined for all architectures and otherwise only >> used with '#ifdef BOTHER'. > > thanks for the report. Is this something that should be #ifdef at the usi= ng side or maybe just fixed for the other architectures. > So far it has been fixed with #ifdef, and this is the first code which uses it outside drivers/tty. So my first tendency would be to fix it on the user side. However, looking into it, I think only alpha and avr32 are affected. Let me submit patches against those and see where it goes. IF: The BOTHER flag should not be involved in setting the baud rate at all.= I've published a patch last week that implements the hci_uart_set_baudrate= properly (in my opinion). Guenter -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" = in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html