From: Marcel Holtmann <marcel@holtmann.org>
To: Ilya Faenson <ifaenson@broadcom.com>
Cc: Guenter Roeck <linux@roeck-us.net>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Frederic Danis <frederic.danis@linux.intel.com>,
BlueZ development <linux-bluetooth@vger.kernel.org>,
"linux-serial@vger.kernel.org" <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 16:43:00 +0200 [thread overview]
Message-ID: <7F15059F-B180-4722-8167-864C4A24CE9B@holtmann.org> (raw)
In-Reply-To: <E0D3336E15B58B4294723AC879BA5E94262266@IRVEXCHMB15.corp.ad.broadcom.com>
Hi Ilya,
>>> 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 using 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).
can you extract this and just submit that version. We might just take that into hci_ldisc.c right away.
However fixing the #ifdef around BOTHER is useful as well since they look unneeded. At least I can not see a reason why a platform would not define them.
Regards
Marcel
next prev parent reply other threads:[~2015-06-15 14:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-15 13:50 Guenter Roeck
2015-06-15 13:58 ` Marcel Holtmann
2015-06-15 14:25 ` Guenter Roeck
2015-06-15 14:38 ` Ilya Faenson
2015-06-15 14:43 ` Marcel Holtmann [this message]
2015-06-15 16:51 ` Ilya Faenson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7F15059F-B180-4722-8167-864C4A24CE9B@holtmann.org \
--to=marcel@holtmann.org \
--cc=frederic.danis@linux.intel.com \
--cc=ifaenson@broadcom.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=linux@roeck-us.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®